Case 3: Resource Metadata Expansion

[djarecka]

This is the use case from the list in #23

This place will be to discuss ideas around the use case, especially around the 3 main components: ingestion, public view and feedback. Below are notes from our initial discussion on August 27.

Ingestion

• we have to think about the types of resource we accept:
  • metadata from data archives: Dandi, OpenNeuro
  • software
• we should be able to extract some information automatically, e.g., from GitHub or Dandi
• we should consider resources as "living objects", and perhaps have system to have current information about the resource (is it still maintained? is it the most recent version?)
• option to provide Related Resources (e..g, publication describing the software)

View

• connection to other resources and show the current information (is it still maintained, etc.)
• connected to the output from the Case 2: Resources Extraction

Feedback

• option to add additional Related Resources (e.g., new publication that uses a dataset) ?

[tekrajchhetri]

Thank you @djarecka for this. One of the point that I see missing is the model to represent the resources itself, which should be in my view the starting point as it would guide and help in other design.

The other thing, I see missing is the extraction of resources information from the publications.

Additionally, I would also like to share the ongoing work on resources extraction. The screenshot below shows different approach one can extract the resources and upon extraction there's an option to correct/update it.

[djarecka]

I opened another case to cover for Resource Extraction: #28