DaMaRO (Data Management Roll-out at Oxford): DataBank & DataFinder

Transcription

1 DaMaRO (Data Management Roll-out at Oxford): DataBank & DataFinder Thursday 25 th October, 2012 James A J Wilson James.wilson@oucs.ox.ac.uk

2 Damaro

3 DataBank Oxford s in-development data archive Intended for datasets with nowhere else to go Links to ORA the Oxford Research Archive (for research papers)

4 DataFinder Catalogue/Registry of research data Intended to hold records for ALL research data produced by Oxford OAI-PMH harvesting of data stores SWORD2 compliant DOIs assigned to records Interfaces directly with DataBank & ORDS Users can register non-electronic data Hierarchical structure

5 DataFinder user journeys Homepage Brief description of DataFinder ACTIONS: Conduct quick search (this should be an option on ALL pages); Go to advanced search; Go to browse; Contribute new record; Go to help page; User Log-in (display welcome Dr. X message if already logged in); View my records (if logged in); Admin options (if logged in with admin rights) (Advanced) Search page Shows advanced search help ACTIONS: submit search Search/Browse results page List short forms of records. Paginated, with filter options down left side of screen ACTIONS: apply filters; view full record; export Admin Home Page Displays records awaiting review (i.e. with status submitted or escalated ) ACTIONS: Review record (select which record to review); alter permissions; sort records; view/add new metadata sources Add/edit sources page Display list of current metadata sources ACTIONS: edit source; add new source (via form) Browse page Presents browse headings. ACTIONS: select browse heading Help Display user help Contribute/edit record Displays metadata form with instructions. Empty if new contribution; prepopulated if editing an existing record. ACTIONS: save record; submit record; submit record with dataset [record set to draft in all cases] Full record view Shows all metadata fields ACTIONS: edit record (if logged in and admin or owner of record). Attempting to edit harvested record will direct user to original record Review record page Displays a full record needing review ACTIONS: edit the record; approve; escalate (with comment); send back (with comment); reject (with comment); cancel Admin permissions page Displays current registered users ACTIONS: Add new admin; remove admin; change admin permissions red lines indicate user must be logged-in to arrive at screen. Attempting to navigate to screen directly will call authentication mechanism Confirm record screen highlight missing mandatory fields ACTIONS: edit; confirm Agree to (one of two) terms of deposit forms ACTIONS: agree [record set to submitted ]; cancel My Records Displays list of user s records with current status clearly indicated ACTIONS: Contribute new record; edit record; sort results; export citations DataReporter results page Displays statistics of records meeting criteria ACTIONS: list records (and view full record from this list); export data/results DataReporter homepage Displays quick report options & custom report builder [user must log in on arrival if not already logged in] ACTIONS: run report Add new user form Lists use details (from CUD?) and Fields to add user ID & role ACTIONS: submit new user

6 Possible statuses of DataFinder records User creates new record Draft *Draft* user still working on the record *Submitted* user has submitted a record for review *Approved* an admin has reviewed a submitted record and declated it suitable for the catalogue without further modifications *Escalated* an admin has reviews a submitted record but decided it needs to be checked by someone senior who may need to call upon specialist help, due to issues regarding commercial or legal agreements, ethics, etc. A note of the issue at stake needs to be added when an admin sets a record to this status. *Referred* the admin has decided that the more/better information is needed before they can approve the record and therefore have referred it back to the submitter. A note of the problem and how to rectify it needs to be appended when this status is set. *Rejected* the admin reviewing the record has decided that there is something fundamentally wrong with it presumably due to misunderstandings regarding the nature of DataFinder. Again, the admin must append a note, this time explaining to the submitter why the record has been rejected. User edits record via editing interface Explanation for referral ed to submitter, with request to re-edit Referred Submitted Reviewer reviews record Reviewer adds a comment to explain why they are setting this status Rejected Explanation for rejection ed to submitter Approved Escalated User confirms that record is complete (approved) record now visible in catalogue Automated thank you sent to contributor Record flagged as escalated on Admin home page Senior Reviewer/Admin picks up escalated record & reads comment, getting 2 nd opinion if necessary

7

8 DataFinder search and browse Keyword & Boolean searching Filtering by embargo status, subject, source, etc. Faceted browsing Full record view Harvested data from sources kept separate from overlaid additions added via DataFinder

9 DataFinder Metadata Records Based on DataCite schema Minimum set required CERIF compliant Additional metadata fields to meet current RC requirements Subject-specific metadata can be added as.xml stream Metadata automatically picked up from earlier tools/services

10 DataFinder DataReporter Generates standard reports Institutional and departmental reports Click-throughs & downloads Personal data publication reports Records lacking key metadata Statistics for REF Customised reports in response to SQL queries Admin-only in first instance

11 Successes Institutional data management policy Integrating training materials developed elsewhere Collaboration between IT Services, Bodleian Libraries, Research Services Provided vision of where the University needs to be Pushing RDM up the University agenda

12 Damaro Challenges Getting rich, consistent metadata Training engagement with researchers Customization of training Embedding RDM training at Divisional & Departmental levels High-level coordination of RDM Developing procedures for postgraduate researchers to deposit data & metadata Sustainability how do we pay for the DataBank / DataFinder services? Measuring impact ROI only apparent over many years, and hard to isolate Evidence of data reuse (particularly of data stored externally)

13 Please us to receive progress updates