From foster@anl.gov Wed Jul 30 10:39:34 2014 Date: Wed, 30 Jul 2014 10:37:58 -0500 From: Ian Foster Reply-To: exec@nationaldataservice.org To: exec@nationaldataservice.org Cc: "Plante, Raymond Louis" , "Bode, Brett" , "Palmer, Carole" , "Pennington, Robert Lee" , "McHenry, Kenton Guadron" , "Namachchivaya, Beth Sandore" , "Wang, Shaowen" , "Butler, Randal L" , "Cutcher-Gershenfeld, Joel Ethan" , "Nahrstedt, Klara" , "Kalantzis, Mary" , "Powell, Danny" , "Cope, William" , "Allen, Gabrielle Dawn" , "Kramer, William T" , "Roloff, Jay R" , "Towns, John W" , "Felarca, Mario Marcaida" , "Redman, Thomas L" , "Melchi, John" Subject: Re: National Data Service (NDS) Weekly Planning Meeting Dear all: I cannot make the meeting today as I am at a DOE workshop. As often I feel someone disconnected from the process. Apparently there is use case documentation being prepared? I have not seen this,a nd I did not see any response to my email a couple of weeks ago asking about use cases. In case useful I enclose below my thoughts on the use cases that we should start with. I believe that these meet needs for MDF. Ian 1.     1) User registers and requests storage allocation; some approval process follows 2.     2) Approved user wants to use NDS to share data with colleagues: can upload data, get a handle [URI? Something else?] that he can share with others o   TBD: Do we want to link storage of metadata with 3.     3) User logs in to NDS and accesses data previously uploaded by someone else, with assigned permissions (read, write, admin) o   Subcase: Access based on handle o   Subcase: Access based on search (see “collections” below) 4.     4) Approved user wants to use NDS to publish data, i.e., create a copy of some data that is subsequently guaranteed to be immutable and persistent. Upload (or maybe apply publish operation to already uploaded data), provide required metadata, get DOI. o   TBD: Where does metadata go? Is there a single place? Multiple places? How does this relate to collections? [I propose that we use Globus collections, and then have a default NDS collection for data that is not assigned to a collection.] o   Need to really nail down DOI policies. E.g., do we support versioning? What does “immutable and persistent” mean? 5.     5) Approved user wants to define a collection on NDS within which approved other users can publish data. This involves defining various policies: required metadata, curation process, etc. 6.     6) One or more use cases involving linking of a published article and a published dataset. Various subcasaes that we may or may not want to implement: o   Data has already been published, is linked to publication. o   Data publication is concurrent with article: thus, access may initially be limited to reviewers, then becomes public when article is accepted. 7.     7) A use case that involves linking with ORCID. I’d like to see this done by linking from the user’s Globus identity to ORCID.  On Jul 30, 2014, at 9:33 AM, Turner-Jones, Kandace wrote: Good morning,   A friendly reminder for our meeting this afternoon. The meeting will again be developer focused and the agenda will be:   * Update on use case documentation * Update on architecture, special architecture video-con/meeting   The meeting will be held in 2100 at NCSA and the call coordinates are also listed below.   Thanks, -Kandace   ............................................................................... .......................................................... à Join Lync Meeting       Join by phone +1 217 332 6338 (Site1-Dialin-region)            English (United States) +1 312 994 8410 (Site1-Dialin-region)            English (United States) +1 888 983 3631 (Site1-Dialin-region)            English (United States) Find a local number   Conference ID: 82072361   Forgot your dial-in PIN? |Help       [!OC([1033])!]