Skip to content

non Data entity data sets #241

@l1ll1

Description

@l1ll1

Hi!
I'm not sure if I'm coming at this problem in the right way but I'll try to give enough background

My researchers have directories full of files. I'd like to encourage them to attach some descriptions (i.e. lets turn it into an rocrate)
I feel like the description should have at least name, description and keywords fields

I feel like using rocrate init and then adding the other fields if the right move

Except of course that the Root entity can't have keywords ... it seems like the intention is to create a Dataset bellow the root entity and attach the description name and keywords here?

Except my researchers are going to get upset if I start making extra sub directories for them, so it seems like I should create a "Conceptual" dataset where the id begins with #

So according to https://www.researchobject.org/ro-crate/specification/1.2/data-entities.html a dataset begining with # would not be a data entity, and therefore doesn't need to end in / and probably shouldn't attempt write because its not a data entity.

def format_id(self, identifier):
has other ideas ....

Whats my best way forward? How should I allow a user to enter keyword data describing their files? If a conceptual dataset is the right way to do it, how can I help alter the code to support conceptual/non-data-entity datasets?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions