Commit Graph
8 Commits
Author SHA1 Message Date
Greg Von Kuster 987df32669 Fix for rendering tools / workflows in target frames, also elimnate the Workflow link in the tool panel as we're now using the menu bar. 2009-02-23 13:52:34 -05:00
Greg Von Kuster 377a5d8981 Add the Libraries tab to base panel and fix the access_libraries tool config for PrognosysBio. 2009-02-23 11:04:27 -05:00
Nate Coraor 42cbc8d893 Set a width hint for the library browser 2009-02-06 14:34:57 -05:00
Nate Coraor b6d561fb42 Allow users to download a selection of datasets directly from the library in an archive format of their choosing. 2008-12-15 16:37:54 -05:00
Greg Von Kuster eeeab78b32 Fixes for accessing libraries from the analysis view. 2008-11-21 09:21:39 -05:00
Nate Coraor 4edc6d6626 Spiffy new library browser interface. Also, dim datasets in your
history on which you don't have permissions.
2008-09-10 10:10:13 -04:00
Greg Von Kuster f50ee0fff3 Added security to libraries. Non-admin users can now only see libraries that contain datasets associated with the user's groups, and each library will only display those datasets that are associated with the user's groups. 2008-08-19 10:04:30 -04:00
Daniel Blankenberg da0b09039c Initial check in of library functionality.
The ui is Very rough, at best.

Libraries can be accessed by users through a new tool under datasources.

Libraries can be created and accessed for modification via a link on the admin page.

Currently, all library datasets are currently associated with the public group.

Tags have been defined (tables and mappings) and can be associated with a dataset or a folder, but there is currenty no interface for displaying or creating these.

Creation and editing of a library should be an admin only function, however this check is not currently present.

The creation/editing page for a dataset is currently hard coded, it should be dynamic (i.e. datatypes and dbkeys)

Brief description of a library:
A library is composed of a name, description and a root folder.
A folder is composed of a name, description, and a parent folder (none when is the root), where a folder can have many or none child folders and datasets.
A library dataset is composed of most of the same attributes as a history dataset, but it is linked via a folder_id to a folder (instead of a history_id to a history).

Ordering of the library is maintained by the 'order_id' attribute of each folder and dataset object (which is populated by the item_count attribute of a folder)
2008-08-12 16:56:26 -04:00