Changes between Version 49 and Version 50 of GSAS
- Timestamp:
- 05/23/13 12:01:40 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GSAS
v49 v50 183 183 || 4e || Review with community || Giridhar || GEC17 || || || || 184 184 || 4f || || || || || || || 185 185 || 3o || Issue 10.1: Is there a way to derive the descriptors in an archive.xml file from descriptors in the other types of metadata.xml files, or at least an initial set of descriptors for the archive.xml file? || Giridhar || || || || || 186 186 187 187 == 4) !DataCite Schema == … … 232 232 || 5l || "iRODS" || Shu || || || || || 233 233 || 5m || "iRODS" || Shu || || || || || 234 234 || 3a || Issue 2.1: How are persistent accounts established for each user in iRODSs? || Shu, Jeanne, Tom/Aaron || 5/22/13 || completed || || Per GIMI workflow discussion: use POST to restful interface on iRODS || 235 || 3b || Issue 2.2: How are storage capacity limits established and enforced for each IRODS user? Are older objects (artifacts) flagged for removal? || Shu || || || || || 236 || 3c || Issue 2.3: How are archive capacity limits established and enforced for each IRODS user? Are older objects (artifacts) flagged for removal? || Shu || || || || || 237 || 3j || Issue 6.1: Need to establish rules if there is a discrepancy in descriptors. || Shu || || || || || 238 || 3k || Issue 6.2: Need to establish rules for changing or removing metadata.xml files. || Shu || || || || || 239 || 3l || Issue 7.1: When using a browser in the Experiment Management Environment (or elsewhere) to view artifacts (files and directories) in the GSAS, how will the associated descriptors (metadata) will be displayed? || Shu || || || || || 240 || 3m || Issue 8.1: After the bag and .tar file have been created and used, is there some cleanup that should be done? || Shu || || || || || 241 || 3n || Issue 8.2: After changes have been made to directories and files, what is the process for recreating the bag and .tar file? || Shu || || || || || 235 242 236 243 … … 280 287 || 7c || || || || || || || 281 288 || 7d || || || || || || || 282 289 || 3d || Issue 5.1: Where is the proxy certificate created? How is the proxy certificate transferred to the GEMINI Measurement Store service? || Ezra || || || || || 290 || 3e || Issue 5.2: What happens if the proxy certificate expires? Is the user notified? How can they load an updated proxy certificate? || Ezra || || || || || 291 || 3f || Issue 5.3: How is the target information transferred to the service? || Ezra || || || || || 283 292 284 293 == 8) Access to GSAS from GIMI I&M Tools == … … 305 314 || 8f || || || || || || || 306 315 || 8g || || || || || || || 316 || 3g || Issue 5.4: How is the iticket transferred to the GIMI portal service? || Cong || 5/22/13 || completed || || Per GIMI workflow discussion: init script gets, pushes || 317 || 3h || Issue 5.5: What happens if the iticket certificate expires? Is the user notified? How can they load an updated proxy certificate? || Cong || || || || || 318 || 3i || Issue 5.6: How is all of the target information transferred to the service agent? || Cong || 5/22/13 || completed || || Per GIMI workflow discussion: init script gets, pushes || 319 307 320 308 321 == 9) Acceptance Tests ==