metadatacenter/cedar-openview

FAIR Data Frontend

cedar-openview's Issues

OpenView editing

Support editing of OpenView instances

Open Metadata Front End

Using the previously developed open artifact functionality, extend Open Server using the new standalone Metadata Editor in read-only mode to display templates and instances.

Publish Open frontend as npm package

Figure out how to publish the Angular 7-based open frontend as an nmp package and add to release script.

Also needed for Docker deployment.

Dockerize Open service frontend

Produce Docker version of open frontend.

Is Angular 7 based so requires different approach than current editor frontend.

Related task for backend: metadatacenter/cedar-project#960

Requires #2]

Integrate form component building into release process

Currently, the cedar-openview application pulls the cedar-metadata-form component from CEDAR's component server via an entry in its index.html file:

<script src="https://component.metadatacenter.orgx/cedar-form/cedar-form-2.4.4-SNAPSHOT.js" type="text/javascript"></script>

The cedar-metadata-form component is first built in the cedar-metadata-form repo and copied to the cedar-component-server repo as follows:

ng build --prod --output-hashing=none

cat dist/cedar-form/{runtime,polyfills,main}.js > custom-elements.js

cp custom-elements.js /Users/dwillrett/Development/git_repos/CEDAR/cedar-component-server/cedar-form/cedar-form-0.0.1.js

We would prefer a more automated process, where the cedar-metadata-form component is published as a library using NPM and imported by the cedar-openview application as a library. The release process would build these components and publish as usual via NPM.

We would also like a development-friendly approach that would allow changes in the component to be picked up by the cedar-openview application witthout going through the library build and reimportation cycle.

Nicer IRI to access JSON representation of open artifacts

We have convenience endpoints to support retrieving the JSON representation of open resources. For templates, it's https://open.metadatacenter.org/templates/ and for instances it's https://open.metadatacenter.org/templates-instances/

So for example, if you have an OpenView template instance with the following URL:

https://openview.metadatacenter.org/template-instances/https%3A%2F%2Frepo.metadatacenter.org%2Ftemplate-instances%2F5a3d43cc-2b28-437d-bcc1-6a22e11ab281

The actual (non URL-encoded) ID of the template instance is:

https://repo.metadatacenter.org/template-instances/5a3d43cc-2b28-437d-bcc1-6a22e11ab281

You can use the https://open.metadatacenter.org/templates-instances/ endpoint followed by the (URL-encoded) ID to get the JSON-LD representation:

https://open.metadatacenter.org/template-instances/https%3A%2F%2Frepo.metadatacenter.org%2Ftemplate-instances%2F5a3d43cc-2b28-437d-bcc1-6a22e11ab281](https://open.metadatacenter.org/template-instances/https://repo.metadatacenter.org/template-instances/5a3d43cc-2b28-437d-bcc1-6a22e11ab281)

Perhaps a nicer convenience IRI would be:

https://open.metadatacenter.org/template-instances/5a3d43cc-2b28-437d-bcc1-6a22e11ab281

(Replace 'repo' with 'open'.)

Can possibly be done with Nginx URL rewriting.

This would also be a nice landing page for artifacts when requesting DataCite DOIs.

"@type" value in output points to bioportal URL instead of ontology's own URL

When modifying a template on CEDAR, if I change the "type" to be, for instance, the Dataset type from the SCHEMA ontology, and then I "populate" the template to get my JSON-LD output, I get this as my @type value: http://data.bioontology.org/ontologies/SCHEMA/classes/http%3A%2F%2Fschema.org%2FDataset, when the @type value should ideally be https://schema.org/dataset.

Without an API key, the http://data.bioontology.org/ontologies/SCHEMA/classes/http%3A%2F%2Fschema.org%2FDataset link does not resolve, so the JSON-LD output object is not technically valid.

Add schema.org markup to OpenView pages

Annotate the HTML wrapper of OpenView pages with Schema.org metadata.

May also need a page elsewhere that links to all OpenView pages so that search engines can find these pages.