Assign handles for profiles and components

[Twan Goosen]

It has been suggested that handles should be assigned for profiles and components so that persistent references to components (from other components and profiles) and profiles (from metadata records) can be made. The details would need to be worked out.

The Component Registry would be responsible for actually assigning the handles and keeping any administration required outside the handle records.

Some thoughts:

• A dedicated CLARIN prefix is available (11372, at GWDG, can be administered via EPIC API v2)
• We need to decide on some regular schema for these handles (e.g. ${CLARIN-PREFIX}/profile/${PROFILE-ID} and ${CLARIN-PREFIX}/component/${COMPONENT-ID}) .
• Part identifiers can be used to link to the XML and XSD expansions of components (e.g. ${CLARIN-PREFIX}/profile/${PROFILE-ID}@xsd)
• Will unpublished components also get a handle?

EPIC API v2 should be used for the creation of handles. CLARIN has a prefix. More information and credentials for an account on the test server is available at EPIC/APIv2.

[Twan Goosen]

All open Component Registry tickets not on a milestone have been put on ComponentRegistry-1.15. Re-assignment to later milestones is likely for some of these tickets.

[Twan Goosen]

Updated info on EPIC API

[Twan Goosen]

​https://github.com/clarin-eric/component-registry-rest/issues/7

[Twan Goosen]

Transferred to GitHub (2.3.0 milestones - ​back end/​front end)