Skip to content

Add a way to distinguish "submissionDocumentation" from "actual data" #8

@ptsefton

Description

@ptsefton

It's been pointed out that the spec doesn't distinguish between supporting files contextualising the data and the actual research data parts of the package. Have a look at how to address this - how is this done in the archive/preservation community? Is there a way to model this in schema.org?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions