Connect Your Repository To SEAD

Encourage more data to be shared, published, and preserved through your repository!

SEADgraphic_with_repositories5

SEAD offers repositories new ways to increase data deposits by allowing them to connect with data producers early while they are still in the process of building their data collections. Using SEAD, repositories can help data producers engage in effective data management and curation practices from the start; thus, helping to enhance the quality of their data publication submissions.

Benefits of Connecting SEAD to your Repository

Reduce the effort required of researchers to publish and preserve data.

Point researchers to SEAD’s secure, team-controlled Project Spaces where they can collaborate, organize, and describe data incrementally over the course of their project, saving them the work of having to describe and organize their data again when it’s time to publish.

Increase participation in your repository!

SEAD provides a pipeline to drive participation by potential contributors to your repository. Our Publication Services create a direct channel between data in researchers’ active Project Spaces and long-term preservation environments. With the click of a button, researchers can set their data on the path to publication and preservation in your repository.

Lower your costs!

Communicate your data submission requirements to your users early in the research process and drastically reduce the time and effort required to process new publication requests. At the time of publication, users will be able to make necessary adjustments to their data and metadata in the Staging Area of their SEAD Project Space based on your repository’s rules about total size, maximum file size, file types, affiliations of authors, metadata, and other requirements. The Staging Area will also provide researchers with immediate feedback and publication status updates.

Advertise your repository through SEAD’s Matchmaker to data producers!

SEAD’s Matchmaker evaluates datasets against the requirements of the participating repositories, and, when there is a match, recommends your repository as a favorable preservation solution.

Two Easy Options to Connect your Repository to SEAD

  • 1

     

    SEAD
    RESTful API

  • Provides streamlined ingestion of scientific data to your repository

    SEAD’s RESTful API funnels well formatted information to your repository allowing you to receive publication requests and process data and metadata to preserve them in your system.


    Supports numerous ingest options

    From completely automated publication requests to requests that channel through your repository’s website to include steps that are part of your existing workflow (e.g. accept your Terms of Use, agree on the licensing terms, etc.). SEAD can even help generate DOIs on behalf of your repository.

  • Check out which other repositories are connected to SEAD via RESTful API:
    openICPSR-front
    IDEALS_logo_2x

    The RESTful API has also proven to be a great option of connecting DSpace and Fedora-based repositories to SEAD

  • 2

     

    SEAD Reference
    Repository Software

  • Enable your repository to handle larger content

    Easily ingest individual publication size from a GB up to TB range, and from tens to hundred thousands of files


    Don’t have a lot of resources?

    Connects your repository to SEAD in minimal amount of minutes!


    Follow best practices in archiving and preservation

    SEAD supports standards-compliant packages and follow the BagIT specification, with metadata documented according to the Open Archives Initiative Object Reuse and Exchange (ORE) specification (serialized as JSON-LD), and integrated with BagIT according to the convention developed within the DataOne project.


    Minimized demands on the repository’s storage file system

    SEAD assembles the data using a parallel Zip archiving library with an internal index. These enable SEAD Partner Repositories to assemble data packages much faster and on common multiprocessor systems (compared to non-parallel approaches), with lower memory and disk space requirements, and fewer, larger packages to store that do not require retrieval of the whole archive to retrieve metadata or individual files.


    Lower requirements for long-term access to published data

    A small application consisting of less than thousand lines of HTML, JavaScript, CSS, and Java software along with a file system, an open source Java web server, and a few open source JavaScript libraries – all that must be maintained by a repository to support long-term access to published data.

  • Meet the IU SEAD Cloud repository:
    IU_SEAD_Cloud_transp

    IU Cloud extended and customized SEAD’s Reference Repository software to work with their remote storage and to also include a local search and some other functionality.

Contact SEAD if you’re interested in learning more about how your repository can partner with SEAD!