Contribute to the DSpace Development Fund

The newly established DSpace Development Fund supports the development of new features prioritized by DSpace Governance. For a list of planned features see the fund wiki page.

Title (Goal)DSpace should allow batch deposits for end users and repository managers through the user interface
Primary ActorEnd User / Administrator
Scope(Optional – notes the perceived design scope. For example, does this use case describe the needs of the overall system or an individual component)
Level(Optional – a general categorization of whether the use case is a very high level summary or almost too low level)
Story (A paragraph or two describing what happens)

A administrative assistant has about 150 digitized technical reports to deposit into the repository. Instead of entering each one by one, she fills out metadata on a pre-established spreadsheet according to directions. She provides a direct link to each report (on a server). She navigates to the appropriate collection and uploads the spreadsheet as a CSV. The repository processes the first row of the CSV to show her an example of what the metadata will look like in the system. She catches an error, deletes the CSV, corrects the mistake in the CSV and reuploads. After confirming that the metadata looks the way she would like it to, she agrees to the license terms, and clicks submit. The repository processes the CSV, ingests the PDFs into the repository, and then emails the admin assistant when the batch upload is complete.

1 Comment

  1. Tim Donohue

    A few notes on this use case:

    The implementation details could likely be slightly different than expressed above and still meet the overall goals of the use case.  In the end this use case seems to primarily require three parts:

    1. A way to batch upload the necessary metadata
      1. CSV seems reasonable as it's used by Batch Metadata Editing as well, plus it's a format non-specific to DSpace
    2. A way to report a confirmation of what entries were processed "successfully" or "failed" prior to saving the content permanently in the system. This would allowing an end user to make changes / fixes prior to saving.
    3. A way to batch upload the associated files. Some possibilities may include...
      1. This could potentially be a Zip of the files (plus metadata/CSV)
      2. An HTML5 multi-file upload form (or similar),
      3. Or some other place to grab the files from (though this would require that the DSpace server has access to that external location)

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.