Page tree
Skip to end of metadata
Go to start of metadata
Title (Goal)End User - Email Deposit
Primary ActorEnd User
ScopeSubmission & ingestion process
Level 
Story (A paragraph or two describing what happens)

Based on ORCID or an institutional staff registry, the repository does a regular crawl for new metadata linked to authors of the institution. Once a new item is discovered that is not yet present in the repository (Duplicate detection!), a workspace item is automatically created with the metadata from the retrieved item.

After this item is created, an email goes out to the author asking him/her to REPLY TO THE EMAIL with the full text as an attachment. The message of the email clearly indicates which version of the file is acceptable, and that replying to the email also implies AGREEING TO THE COLLECTION LICENSE.

The email reply that contains the attachment gets processed automatically by the repository, and pushes the item further into the workflow (or straight into the repository if no workflow is defined for the collection).

4 Comments

  1. This requires:

    • A definition of a list of ORCIDS or authors for which the daily crawl needs to happen
    • Duplicate detection for the matched items
    • A way for a user to set a default collection in his/her EPerson account, otherwise there's no way to know in which collection to deposit the item
    • A way for a user to indicate in the EPerson account that he or she WANTS the automatic crawl for his/her name and use email submission

     

  2. Also requires a pre-existing EPerson for each email/ORCID that will be crawled.

  3. Cross linking this with the Integrations - Personal Identifiers (ORCID) use case (which still needs its own fleshing out), just cause this seems like it'd require some level of enhancement for how DSpace deals with personal identifiers.