...
Automatic minting of DOIs for visits
Identify visits that shouldn’t be opened (including BAGs and commercial) – Diamond.
Email PI once visit is over to update team or say DOI not to be created (exceptional circumstances) – Diamond.
Automatically mint DOI 2 days after visit ends for eligible visits
o After this point the experimental team will be fixed as a permanent record of the experiment.
DataGateway should allow the PI for a visit to open the visit data to everyone after agreeing to terms and conditions.
o No user selection of data: all visit data other than ‘hidden’ data will be open.
Data Download:
DataGateway should allow anonymous users to download open data.
DataGateway should allow access to data by investigation team.
Allow PI to manage restricted data access by adding people who are not in the team or removing access to anyone (except themselves) – Diamond.
Hiding data:
Hidden data is data files, sets and visit that are not made open, even if the set or visit they belong to is opened.
Hidden data will be accessible in DataGateway to registered users with data access rights to the related visit.
User uploaded auxiliary data should be hidden automatically in the short term.
Other data from session DOIs and user created publications can only be hidden by email request to Diamond, neither case is editable by users after publication.
Possible to make hidden data unhidden in the future – requires policy change.
Data upload:
Users will have the ability to upload data to the archive, relating to a specific session, at any stage (e.g. auxiliary/processed data). User-uploaded data will be covered by the same restrictions described under ‘hiding data’.