Materials Data Centre

Here's our first use case for EP2DC. It is to allow a user to attach datasets to their academic publication when they upload it to EPrints. The data can be seamlessly sent to the Materials Data Centre via the EPrints interface.

UC title          
UC‑01—uploading test data to an EPrints repository

Context          
Capturing the test data reported in an open access publication and cross‑referencing the data to publication.

Brief UC          
Tests are performed the context of a research project according to recognised procedures.  The generated data is conserved in a standard electronic format.  The work is reported in an open access publication that is submitted to an EPrints repository together with the corresponding test data.

Fully Dressed UC
Scope                  EPrints data inject module.
Level                   User‑goal.
Primary Actor   Scientist—the person responsible for performing the test has an interest, and is perhaps even obliged to store the data. Stakeholders     
Analyst—needs access to data.                            
Data reuser—interested to access the data in anticipation of using the data in a different context.                            
Funder—needs to be able to audit the work performed.        
Time—any delay conserving the data has a direct impact on data quality.                         
Machine—machine operating system and application suite determines data format.

Preconditions    
Data set is generated according to a recognised procedure and a corresponding publication is uploaded to EPrints.

Postconditions   
Data sets are archived at a data centre and cross­‑referenced to the open access publication to which they correspond.

Main Success Scenario
1. As part of the process of entering metadata, XML data sets are uploaded.
2. Data set/s validated against a public domain schema definition.
3. Scientist selects a remote data centre to manage the data set/s.
4. Data set/s transferred to remote data centre/s.

Extensions
1a. The data is already available at a remote data centre.
1. Scientist browses remote data centre and selects data set.
2. The manuscript is cross referenced to the data set.
2a. There is no suitable schema.
1. Validation is performed against a local schema.
2b. Data fails validation.
4a. Data cannot be transferred to remote data centre.
1. Data set/s stored at the EPrints repository until such time as the remote data centre is available.
2. Data set/s transferred to remote data centre.