Changes between Version 44 and Version 45 of GSAS
- Timestamp:
- 05/22/13 18:10:43 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GSAS
v44 v45 220 220 || 5c || Establish authentication for each user based on certificates, and also proxy (delegated) certificates. || Shu and Jeanne || GEC15 || completed || || || 221 221 || 5d || Establish directory structure in storage service for each user to accommodate multiple experiments, and directory structure for each experiment (consider "bag") to include all objects (artifacts) associated with that experiment, including one or more descriptors (metadata) within XML files (following the GENI descriptor schema) || Shu, Harry and Giridhar || GEC15 || completed || || || 222 || 5e || Provide multiple interfaces (including icommand, restful http, and web) to allow authenticated user to view, search and curate their objects (artifacts) || Shu || GEC15 || completed || || restful http can come later ; or should we do it soon, to be used to create user accounts?||222 || 5e || Provide multiple interfaces (including icommand, restful http, and web) to allow authenticated user to view, search and curate their objects (artifacts) || Shu || GEC15 || completed || || restful http can come later || 223 223 || 5f || Provide interface to allow user to define an object to be archived (where the object may range from a large directory to a single file), include a descriptor (following the GENI descriptor schema), assign a persistent Digital Object Identifier (DOI, or "handle"), and decide when to push it to archive service. || Shu || GEC16 || in progress || || || 224 || 5g || Establish an archive service that provides long-term and reliable storage, with access via a DOI from the global handle service, with access following a local policy included in archived object. (Include at least two policies: give the object to anyone, or give the object only to its owner.) || Shu || GEC17 || in progress, discussed with Antoine || || Need example metadata.xml files, including key values. Should iRODS validate xml schema (syntax)?||225 || 5h || Add rules to process incoming descriptors in xml files, and store info in iCAT (3-4 weeks) || Shu, Antoine || GEC17 || || || ||224 || 5g || Establish an archive service that provides long-term and reliable storage, with access via a DOI from the global handle service, with access following a local policy included in archived object. (Include at least two policies: give the object to anyone, or give the object only to its owner.) || Shu || GEC17 || in progress, discussed with Antoine || || || 225 || 5h || Add rules to process incoming descriptors in xml files, and store info in iCAT (3-4 weeks) || Shu, Antoine || GEC17 || || || Need example metadata.xml files, including key values. Optionally, iRODS to validate xml schema (syntax) and verify mandatory elements || 226 226 || 5i || Add rules to move object to public archive service, and make any changes (3-5 weeks) || Shu, Antoine || GEC18 || || || || 227 227 || 5j || Integrate archive service into handle service (1 week) || Shu, Antoine || GEC18 || || || || 228 || 5k || Provide interface to iRODS to allow GENI Experimenter Portal to create iRODS user accounts || Shu, Antoine || GEC17 || || || Should this use POST to restful interface?||228 || 5k || Provide interface to iRODS to allow GENI CH Portal to create iRODS user accounts || Shu, Mike || GEC17 || || || Work with Tom/Aaron to define API; GENI CH Portal acts as iRODS user; use POST to restful interface, and provide only basic functions by GEC17; later, add more functions || 229 229 || 5l || "iRODS" || Shu || || || || || 230 230 || 5m || "iRODS" || Shu || || || || || … … 252 252 || '''ID''' || '''Description''' || '''Who''' || '''Due''' || '''Status''' || '''Demos''' || '''Notes''' || 253 253 || 6 || "Experiment Artifact Management Tool" || || || || || || 254 || 6a || || who? || || || || p/o Cong's work on GIMI init script?||254 || 6a || || Cong || || || || see GIMI || 255 255 || 6b || || || || || || || 256 256 || 6c || || || || || || ||