Skip to content

change separate collections to one "resources" collection #40

@meganrm

Description

@meganrm

Use Case

we don't always know which resources someone wants to add

Acceptance Criteria

one resource collection:
has Type: "software tool", "dataset" etc

can add as many as you want

Details

can the flow be: pick a type, ie "Software" and get specific fields for that?
ie software we'd want to have a README/Quickstart link

Metadata

Metadata

Assignees

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