Accel Metadata Model issues and tweaks

[michael-conway]

Discussion on accel core metadata model design, what's missing, what's unclear, what should be in roadmap discussions

[michael-conway]

Hey @pateldes @amlantalukder @schmittcp-nih this is where we can talk about design issues and needs in the metadata model for accel

[michael-conway]

We need to formalize the requirement that each resource we ingest must have a unique identifier and a way to relate that identifier to the original source (e.g. a hash of the URL endpoint, a doi). This can be put into the accel ingest and dissemination interfaces like resolve_resource_id() or something...we need to be able to explicitly relate back from an entry in the accel database to the source so we can validate or update

[michael-conway]

Looking at dataverse it might behoove us to formally capture license information, including a controlled vocab of license types and their urls..

.we can make use of the 'custom' license type in dataverse to perhaps capture some of what's already in accel..

[michael-conway]

ahh...

https://ehsodsvld01.niehs.nih.gov/api/licenses

these are the two:

{
"status": "OK",
"data": [
{
"id": 1,
"name": "CC0 1.0",
"shortDescription": "Creative Commons CC0 1.0 Universal Public Domain Dedication.",
"uri": "http://creativecommons.org/publicdomain/zero/1.0",
"iconUrl": "https://licensebuttons.net/p/zero/1.0/88x31.png",
"active": true,
"isDefault": true,
"sortOrder": 0,
"rightsIdentifier": "CC0-1.0",
"rightsIdentifierScheme": "SPDX",
"schemeUri": "https://spdx.org/licenses/",
"languageCode": "en"
},
{
"id": 2,
"name": "CC BY 4.0",
"shortDescription": "Creative Commons Attribution 4.0 International License.",
"uri": "http://creativecommons.org/licenses/by/4.0",
"iconUrl": "https://licensebuttons.net/l/by/4.0/88x31.png",
"active": true,
"isDefault": false,
"sortOrder": 2,
"rightsIdentifier": "CC-BY-4.0",
"rightsIdentifierScheme": "SPDX",
"schemeUri": "https://spdx.org/licenses/",
"languageCode": "en"
}
]
}

I'll have to see how to add custom terms but looks like it must be one of those. I think this is the license for the dataverse entry not the underlying data source, we can maybe dodge this question

[michael-conway]

licenses can be added via:

/licenses:
get:
operationId: Licenses_getLicenses
responses:
"200":
description: OK
post:
operationId: Licenses_addLicense
responses:
"200":
description: OK

[michael-conway]

author data in dataverse?

subject? Would this map to domain? to keyword?

[michael-conway]

subject appears not to be configurable perhaps there is some sort of domain -> subject translation that can happen

[michael-conway]

topic versus keyword versus subject in dataverse

[michael-conway]

are we missing grant info in our model?

[michael-conway]

"Kind of Data" in dataverse model? Figure out purpose..

 ```json
      {
        "typeName": "kindOfData",
        "multiple": true,
        "typeClass": "primitive",
        "value": [
          "KindOfData1",
          "KindOfData2"
        ]
      },