Versions Compared

Old Version 7

changes.mady.by.user Andrew McLean

Saved on

compared with

New Version Current

changes.mady.by.user Ignace Deroost

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date & Time

  • January 12 16:00 UTC/GMT - 11:00 EST

...

Bram Luyten (Atmire) will give a short demonstration to show what the implications are on the DSpace submission forms and metadata schema through: https://join.me/atmire_meeting. In the event that the live demonstration would somehow fail, we will be referring to the screens in this PDF.

Participants are invited to share from their national and institutional context if the RIOXX profile (or selected fields) makes sense for them. Everyone is invited to think about the issues that could occur if the profile would be merged into the DSpace core, which would already have 2 following concrete implications:

  • Do we want to preserve DSpace's default list for dc.type? Should we enable both the DSpace dc.type vocabulary as well as the RIOXX one (which might be confusing for submitters).
  • DSpace has a free text field for bitstream descriptions, while RIOXX has a controlled vocabulary. Should we keep and offer both?
  • RIOXX is very explicit about the fact that the metadata should correspond with a single file. However, dspace offers uploading of multiple files in one item. The Atmire patch addresses this by using the "primary" bitstream, as the file that is relevant for RIOXX. In this way, both approaches are compatible but it's worth discussing if someone feels different.
  • Is the funder/project lookup submission step something we would enable by default or not. Considerations:
    • Leaving it off is making it more complex for people to enable/start using it.
    • Leaving it on by default makes it more complex for people who want to DISABLE this / not use it.
    • Further information: item-submission.xml for RIOXX and Submission User Interface documentation

Other topics

Preparing for the call

RIOXX

...

Meeting notes

 ...

RIOXX Application profile

In general, DCAT concluded the RIOXX standard could also be beneficial for Institutions not having to comply with the UK Research Excellence Framework (REF).

However, RIOXX currently does contain obligatory metadata fields which are not relevant for many institutions outside of the UK. Examples are the 'project' and 'funder' metadata field (see below). For this reason the current RIOXX standard would not be suited for use as the default in the dspace codebase. It would however be convenient to include RIOXX in the DSpace codebase as an optional standard. This way UK institutions would not have to manually adopt the patch. Institutions from outside the UK would also be able to easily adopt the RIOXX standard in case they would prefer RIOXX over the current standard.

Deviation from current DSpace standard

For users familiar with the current metadata standard the introduction of RIOXX may be somewhat confusing when it comes to the selection of content type (dc.type) as the RIOXX standard uses its own content type (rioxxterms.type). These fields do have a substantial overlap in vocabulary.

Rioxx added some fields to the describe tabs in the item submission form:

  • License URI: The two url's below the input field are there for the submitter's convenience. In case there is no license url available one of those two licenses can be used. They are the UK legal default.
  • License start date
  • Date accepted
  • Version

The RIOXX patch also adds a new tab to the submission form, the 'Project' tab. This tab includes two metadata fields: 'Project' and 'Funder'. There is lookup functionality available for both of these fields. The 'funder' lookup is automatically populated by fundref. Both of the metadata fields are mandatory, however this may not be relevant for users outside of the UK, as it was specifically developed for the UK REF compliance. It might be convenient to add the option to choose 'Not Applicable (N/A)' as a value for such users. This way they could include this field in case it would add useful data to some, but not necessarily all of their items.

RIOXX OAI endpoint

A RIOXX item should only contain one file, while DSpace items can contain multiple bitstreams. For this reason the RIOXX patch allows you to mark one of the bitstreams in DSpace as the primary bitstream. This will be the only bitstream presented at the RIOXX OAI endpoint.

The RIOXX endpoint does not cause any conflict with other endpoints, instead it runs alongside of them.

The RIOXX OAI endpoint will only be presented with items with completed mandatory metadata. In case your repository would contain items which are not relevant for RIOXX (e.g. electronic theses and dissertations), and thus which will not contain all the metadata required for RIOXX (for example the project field will not be completed), these items will not be available through the OAI endpoint.

ORCID

Next to adding some metadata fields to the current standard, The RIOXX patch also includes an ORCID integration for DSpace 3 & 4. This functionality was backported from DSpace 5. Including the RIOXX standard in the DSpace codebase would thus facilitate the use of ORCID on some previous DSpace versions.

DSpace Working groups

The DSpace Marketing Interest Group launched 5 new working groups:

  • Mission and Vision Statement
  • DSpace Stories
  • Engaging the Community 
  • Increase Membership 
  • Communication

David Lewis is facilitating the Mission and Vision Working group. He would like to receive DCAT feedback on his draft document:
https://drive.google.com/folderview?id=0B6gsx378OoLAQ2pOYXl5Rm9rN0E&usp=sharing

Please send comments or suggestions to David: dlewis@iupui.edu

If you would like to volunteer to be a member of any of the working groups, please express your interest to David via email: dlewis@iupui.edu

Call Attendees