116 | | || 2a || Issue 2.1: How are persistent accounts established for each user in iRODSs? || || || || || || |
117 | | || 2b || Issue 2.2: How are storage capacity limits established and enforced for each IRODS user? Are older objects (artifacts) flagged for removal? || || || || || || |
118 | | || 2c || Issue 2.3: How are archive capacity limits established and enforced for each IRODS user? Are older objects (artifacts) flagged for removal? || || || || || || |
119 | | || 2d || Issue 5.1: Where is the proxy certificate created? How is the proxy certificate transferred to the service? || || || || || || |
120 | | || 2e || Issue 5.2: What happens if the proxy certificate expires? Is the user notified? How can they load an updated proxy certificate? || || || || || || |
121 | | || 2f || Issue 5.3: How is the target information transferred to the service? || || || || || || |
122 | | || 2g || Issue 5.4: How is the iticket transferred to the service? || || || || || || |
123 | | || 2h || Issue 5.5: What happens if the iticket certificate expires? Is the user notified? How can they load an updated proxy certificate? || || || || || || |
124 | | || 2i || Issue 5.6: How is all of this target information transferred to the service agent? 22 || || || || || || |
125 | | || 1 || || || || || || || |
126 | | || 1 || || || || || || || |
| 119 | || 2a || Issue 2.1: How are persistent accounts established for each user in iRODSs? || Shu, Jeanne || || || || || |
| 120 | || 2b || Issue 2.2: How are storage capacity limits established and enforced for each IRODS user? Are older objects (artifacts) flagged for removal? || Shu || || || || || |
| 121 | || 2c || Issue 2.3: How are archive capacity limits established and enforced for each IRODS user? Are older objects (artifacts) flagged for removal? || Shu || || || || || |
| 122 | || 2d || Issue 5.1: Where is the proxy certificate created? How is the proxy certificate transferred to the service? || Ezra || || || || || |
| 123 | || 2e || Issue 5.2: What happens if the proxy certificate expires? Is the user notified? How can they load an updated proxy certificate? || Ezra || || || || || |
| 124 | || 2f || Issue 5.3: How is the target information transferred to the service? || Ezra || || || || || |
| 125 | || 2g || Issue 5.4: How is the iticket transferred to the service? || Cong || || || || || |
| 126 | || 2h || Issue 5.5: What happens if the iticket certificate expires? Is the user notified? How can they load an updated proxy certificate? || Cong || || || || || |
| 127 | || 2i || Issue 5.6: How is all of this target information transferred to the service agent? || Cong || || || || || |
| 128 | || 2j || Issue 6.1: Need to establish rules if there is a discrepancy in descriptors. || Shu || || || || || |
| 129 | || 2k || Issue 6.2: Need to establish rules for changing or removing metadata.xml files. || Shu || || || || || |
| 130 | || 2l || 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 || || || || || |
| 131 | || 2m || Issue 8.1: After the bag and .tar file have been created and used, is there some cleanup that should be done? || Shu || || || || || |
| 132 | || 2n || Issue 8.2: After changes have been made to directories and files, what is the process for recreating the bag and .tar file? || Shu || || || || || |
| 133 | || 2o || 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 || || || || || |
| 134 | || 3 || Establish GENI policy on sharing research results || || || || || || |
| 135 | || 3a || DRAFT policy ( 2 pages) || Larry/Giridhar || 6/1/13 || || || || |
| 136 | || 3b || Review with GPO || Larry/Giridhar || 6/1/13 || || || || |
| 137 | || 3c || Review with community || Larry/Giridhar || GEC17 || || || || |