Staging Area Design

• Wiki page for design: 
• Michael's Flow diagram: 
  
  Live Objects: Dataset and Collections in a Space. Anybody can change/add/modify.
  
  
• Curator Picks some of the Live Objects and start the process of submitting that dataset or collection. 
  
  1st Question: What is for us a Curation Object? Is it just a copy of the live object, and the updates are kept separate. They are basically all that we selected. And we put it in the Curation Area as an object that we are working on. 
  There is an entry in the staging area with all the information that was available when you put it on the staging area. 

What happens if the original one is updated?

The curation Dataset has a link to the original Id of the dataset. Do we keep track in the original dataset to the live object? 

Curation Area is specific for each space. 

Anyone else in the space/group. Everybody can see it. 

There is a staging area per space. There is a staging area that is private? 

• Step: Tell me what repositories will accept this curation object.

1. Identify what repositories are compatible with what I want to do.
2. Help me refine what the repository needs for me to do a submission. If the repository requires an abstract. We need to provide a way to add the abstract to the dataset. Or other kind of metadata/requirements for the datasets/collection in order to be published. 

a) identify the datasets you want to publish. And create the curation object.

b) Call the matchmaker. I am interested in this thing. What repositories are compatible with this?

c) Clowder should save the preferences for the repositories someone wants to publish.

d) It is unclear what the matchmaker accepts as input. 

e) Publication Object is the Curation Object + DOI (Digital Object Identifier). The returned object from the repository. 

TO BUILD: 

• Concept of a staging area per space. 
• Take a live dataset/collection and create a curation object or dataset object. 
• In the curation area you can see all the curation objects that has been started by everyone in the space. 
• Store user preferences for publication. (Preferences for calling the matchmaker)
• Add rules to the matchmaker that are attributes of the data. 
• Input to matchmaker: User Preferences + attributes of the data.
• Show suggestions to the user. About missing information that the repository needs/wants. 
• This will be a plugin for Clowder.
• Create multiple plugins for submitting the code a C3PR plugin, Ideals plugin fedora plugin. 

Sprint 1 - Curation Projects. 

• Create a staging area per space
• Create a curation object: creator, date, title, description, curator, dataset, collections, list of copies, blob, metadata, object
• Store users preferences for publication

Optional: 

• Edit Curation Object

Sprint 2 - Matchmaker Calls 

• Wizard Flow 
• Call Matchmaker

Sprint 3 - C3PR Calls. 

• Refine Metadata

Sprint tasks:

1. Staging area per space [Indira]
   1. standalone plugin
2. Create curation object [Yan]
   1. Select  dataset and collections from space [Luigi]
3. Submit for publication (separate plugins?) [Rob]

1. Call matchmaker and pick repository (separate plugins?)
2. Refine metadata
3. Store user preferences for publication in profile
4. Store published object (everyone in space can see them)

1. Edit curation object
2. List curation objects and published objects that a dataset/collection are part of

1. Create curation object
2. Matchmaker query and selection
3. Editing of metadata and submission to repository

1. Who can see the curation objects?

1. curation object -> publication object
2. repositories preferences
   1. a repository says what options it provides
   2. user might have preferences set in their profiles in the spaces
      1. generally speaking I want things free
      2. but in one instance I might be willing to pay
3. attributes of the content vs attributes of the repositories
   1. "I would like"
   2. "I have images"
4. "if my dataset doesn't have license, assign creative common"
5. preference / requirements