TreeBASE Submission Integration

From Dryad wiki
Revision as of 11:31, 29 April 2010 by Ryan Scherle (talk | contribs) (User submites to TreeBASE, Dryad harvests only)

Jump to: navigation, search

Status: Nescent and Yale are currently finalizing the design and beginning implementation.

Overview

Authors who submit content to TreeBASE or Dryad will be have the option to make their content appear in both systems.

TreeBASE content will be searchable through Dryad, even if the author has not explicitly included the content in a Dryad data package.

This integration will be based on the following technologies:

  • BagIt -- A lightweight format for packaging digital content and ensuring that it is transferred intact.
  • OAI-PMH -- A protocol developed by the digital library community to allow harvesting of metadata from remote repositories.

We are evaluating the SWORD protocol to manage the transfer of BagIt packages, but we have not yet determined whether SWORD will be lightweight enough to justify its use.

Use cases

User submits to Dryad first

  1. User submits Nexus to Dryad, and pushes "send to TreeBASE" button.
    • Button says "I want to deposit my tree(s) in TreeBASE and enhance the description there. I realize that any annotations I create in TreeBASE will also be released under the CC0 license."
  2. Dryad pushes object to TreeBASE. (This is before the object is curated in Dryad)
  3. User goes to TreeBASE and completes record.
  4. Dryad harvests TreeBASE content.

User submits to TreeBASE first, links from Dryad record

  1. User submits/edits package in Dryad and includes a TB ID
  2. Is it already in Dryad (via harvest)?
    • If so, create internal links in Dryad
    • If not, ask the user for their access code.
    • If that doesn't work, tell them to just upload their nexus file as a separate data file
  3. Dryad adds TB ID to the record, and TB will be able to check up on it.
  4. Also add an alert for Dryad curators to follow up.

User submites to TreeBASE, Dryad harvests only

  • Treat as any other harvested content (second-class)

Workflow

  1. User submits to Dryad (and completes the submission).
  2. User is presented with a button "Also submit this content to TreeBASE"
  3. When the button is pressed, citation data and all uploaded nexus files are packed into a BAGIT package and pushed onto TreeBASE
    1. TreeBASE has a PUT RESTful service for receiving data (later this may be reimplemented as a SWORD service)
    2. TreeBASE only accepts the PUT if the sender's IP is within the Dryad range
  4. TreeBASE responds by returning an URL and Dryad tells the user to "click on this" to finalize your submission in TreeBASE
  5. Clicking on the link takes the user to a special log-in page in TreeBASE; upon logging in, TreeBASE is triggered to unpack the BAGIT and create a submission based on the contents

Process for submitting to TB

Minimum Requirements

  • nexus file
    • at least one tree OR at least one matrix
    • if there is a tree and a matrix, the taxon labels must match up.
    • must be "understood" by Mesquite
  • citation
  • analysis info linking matrices and trees

Detailed Process

  • create account
  • login
  • create new submission
  • type title
    • the submission gets a PURL at this point
    • the PURL can have a code added for reviewer access
  • fill in citation
    • minimum: year, title, journal name (or book/section title)
    • journal names auto-suggest as you type
  • add authors
    • minimum: at least one author (with first name and last name)
    • must always search for an existing author first, even if you know they're not in the system
    • allows reordering or deleting authors while you're in the process
  • upload file(s)
    • minimum: must be nexus, as described above
  • (optional) add notes
    • this is a textarea, with a reasonable character limit (not enough for a readme file)
  • (optional) edit details for matrices
  • (optional) edit row segment template
    • minimum: row ID, start index, end index
  • (optional) provide more details for trees
  • (optional) taxa
    • match all named taxa against ubio or ncbi
    • although the cleanup is optional, the TB editor may reject it if it's not cleaned up
  • analysis
    • minimum: create an analysis with at least one step. Typically, this will be a matrix that is processed to create one or more trees.
    • minimum: otu labels must match in the analysis steps
  • when initial submission complete, user clicks "change to ready state"
    • this triggers the curator to look at it
    • user can leave items as "in progress" as long as they want -- this is a "poor man's embargo" system

Open Questions

  1. Can Dryad records be transferred immediately, or must they be approved by a Dryad curator first? If records are transferred before curator approval, when is the permanent ID assigned?
  2. Is it possible to carry over authentication? (single sign-on) Can/should Dryad track user account info on other systems? (or will everyone move to DataONE authentication?)
  3. Does the user have to press a button to submit to TreeBASE, or could it just be automatic? If we could link the user accounts, the submission could just show us when the user logs into TreeBASE.
  4. Should TreeBASE have a "pull" method, where users logged in to TreeBASE can import content with a Dryad ID?


Random Notes

  • TB does not make content available until the associated article is published
  • (new) TB only has one identifier, which is used all the way through the process
  • TB has thousands of in-progress submissions, which are waiting for the publication to be accepted.
  • Dryad often knows that an article has been accepted, and should tell TB about this
  • TB may have an embargo process, which Dryad should use for embargoed items

Relevant Text from the Grant Proposal

  • "[handshaking] so that, where required by the journal or requested by the author, data will simultaneously be deposited in Dryad and... TreeBASE."
  • "Dryad will collect any metadata required by the target database that has not already been captured, submit the pertinent data to the target database using a non-interactive programmatic gateway, and obtain the submission status, accession numbers, or possible error messages from the target database."
  • "For TreeBASE, we will design and implement a robust, web-service based submission Application Programming Interface (API). An extensive redesign of TreeBASE by the CIPRES project (www.phylo.org) is scheduled for release in 2007. However, it currently lacks a submission API. The software to be added will include the automated data validation steps that are part of the new TreeBASE submission process (e.g. validating the NEXUS format, matching terminal taxa against the uBio NameBank). When TreeBASE rejects a submission, the depositor will be notified, advised how to correct the problem, and asked to resubmit. "


See also: TreeBASE OAI Provider