omeka-s-modules / orcidconnector Goto Github PK

There needs to be a check on whether someone already has an Orcid Id, and branch display of that.

Related to #2, we need to produce an interface for updating, not just connecting to, Orcid data.

There's a deep layer of crud just based on testing/developing code in the controller and view that doesn't belong there. It's about time to separate those out to their appropriate places.

Alas, that also means some database updates, and checks on data validitity

I'd like to avoid importing all of schema.org to make the connector work, which will mean some work to figure out the appropriate subset, and how to carve it off from other schema.org data, if possible.

See https://groups.google.com/forum/#!topic/orcid-api-users/hzZJxw_BfJE

For testing/dev, there's a method to create a new template stuffed into the controller. That belongs in the module install.