Versions Compared

Key

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

...

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.

Other topics

...