Dataverse Feature in Archivematica

dataverse.feature

Feature: Create an Archival Information Package (AIP) from a dataset from a 
         Dataverse repository

    Alma is a Dataverse and Archivematica user
    And they want to preserve their datasets outside of Dataverse
    On their own choice of digital file storage
    So that their data can persist independently of any repository system

    Background:
        Given the Storage Service is configured to connect to a Dataverse
        Repository 
        And the Automation tools are configured to monitor active transfers
        periodically

    Scenario: Seek and return datasets
        Given a successful connection to a Dataverse repository
        When a list of datasets is returned 
        Then the Storage Service provides that list to Archivematica

    Scenario: A connection cannot be made to a Dataverse repository
        Given an unsuccessful connection to a Dataverse repository
        When a connection error is returned
        The Storage Service will create a log entry for each unsuccessful 
        attempt

    Scenario: A dataset is selected for transfer
        Given a dataset is selected for transfer
        When the dataset is transferred into a directory monitored by the
        Automation Tools
        Then the dataset is manipulated into a transfer compatible SIP
        And the Archivematica transfer workflow is approved

    Scenario: A SIP preserves the dataset relationships
        Given a dataset is read by the automation tools
        When the dataset is evaluated as having multiple component parts
        Then the SIP will describe the relationship between component parts
        And each component part will be given its own descriptive metadata 
        section

    Scenario: A suitable PREMIS agent is described in the transfer metadata
        Given a dataset is read by the automation tools
        When the dataset is successfully transformed
        Then the PREMIS linking agent for the derivation must be described as 
        Dataverse

    Scenario: The dataset AIP preserves Dataset relationships
        Given a SIP of type Dataverse arrives in the Ingest workflow
        When the AIP metadata is generated from the SIP
        Then the AIP will transfer metadata components related to the Dataverse
        relationships into the AIP metadata structure

    @Future @phase3 @wip @ToVerify
    Scenario: A dataset version is found to have been updated
        Given a successful connection to a Dataverse repository
        When a list of datasets is returned
        And a new version of a dataset is found to be available
        Then a new automated transfer will be approved
        And a relationship will be established between the new AIP and its
        previous versions using an Archival Information Collection (AIC)

object-storage.feature

Feature: The storage service can connect to multiple different storage types

    Alma is a systems administrator
    And wants to offer their company multiple different storage types
    So that different mechanisms can be selected based on different requirements
    such as operating costs, performance, reliability and so forth.

    Scenario: A pipeline wants to retrieve a package from an object store
        Given the storage service has been configured to connect to an object
        store
        When Archivematica calls up a package with a given UUID
        Then the Storage Service connects to the object store
        And the Storage Service returns a pointer to the package on that system

    Scenario: A pipeline wants to store a package on an object store
        Given the storage service has been configured to connect to an object
        store
        When Archivematica sends a package to the Storage Service
        Then the Storage Service will push the package into the storage system
        And signal to Archivematica the successful transfer of that information