Preparing for the Metadata Explorer UI demo

[acu192]

In order to fulfill the needs of the Metadata Explorer demo (see mockups here), we need to add 8 new fields to the dataset schema (i.e. this file) following the schema for the Dataset type outlined in schema.org's Dataset type.

Those 8 fields that need to be added are:

• copyrightHolder
• copyrightYear
• creator
• license
• provider
• dateCreated
• dateModified
• exampleOfWork

Next we need to publish a method for retrieving the metadata given a target (i.e. a string representing a file path to, presumably, a data file). The interface should be here, and the implementation here.

[saulshanabrook]

This sounds good.

Next we need to publish a method for retrieving the metadata given a target (i.e. a string representing a file path to, presumably, a data file).

Could be a string for the URL? So for a file this would be file:///data.csv for example.

[acu192]

Yeah, I was imagine the same as we did for the commenting target. (here)

I'll start working on the UI assuming we have these fields, and we can plug them in once they exist.

[xmnlab]

sounds pretty good. I will add this fields today. I am also studying how feasible is the integration with https://github.com/cape-io/graphql-schema-org .. but for now I will just add this fields in the schema type/resolver/datasource.

[xmnlab]

@acu192 do you could understand the difference between "author" and "creator" ? should we keep both?

[acu192]

@xmnlab Good point. On the Dataset page, under creator it says "This is the same as the Author property for CreativeWork." (Also note that Dataset derives from CreativeWork.)

Therefore I would say we don't need creator. Unless others point out something we're not seeing...

[xmnlab]

@acu192 I added both for now ... we can remove any one any time https://github.com/jupyterlab/jupyterlab-metadata-service/pull/13

I will added the code for frontend there.