facet for CMDI profile

[dietuyt]

Would be nice to have a facet showing the name of the CMDI profile used. When displaying this (in single record view) it could link to the component registry, like eg:

​imdi-profile-instance

Check with Twan? if we can change the names in case they do not make sense without influencing the generated XSDs. In case that is not possible we'll probably have to use a fallback mapping the component ids to a readable label. (but that could also be implemented at the component registry as a readable name will be benifitial there too)

[twagoo]

On the XML level this should not pose a problem. You could simply have:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CMD_ComponentSpec isProfile="true" xsi:schemaLocation="http://www.clarin.eu/cmd http://www.clarin.eu/cmd/general-component-schema.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <Header>
        <ID>clarin.eu:cr1:p_1297242111880</ID>
        <Name>Annotation tool pretty name</Name>
        <Description>Description of a tool
adapted from adept for interviews</Description>
    </Header>
    <CMD_Component CardinalityMax="1" CardinalityMin="1" name="AnnotationTool">

The name of the root component is relevant to the schema, not the name in the header.

At this moment this can only be changed through the ComponentRegistry admin area, but we could extend the UI to allow users to specify a 'friendly name' themselves.

[dietuyt]

Ok, I will go over the profiles and enhance the header names then. @Twan: would probably be good after all to have a GUI element to change that name - we need to think about this, because I remember that we did away with it in the past because it was too confusing, so we need to make it clear what it means.

[twagoo]

Replying to dietuyt:

Ok, I will go over the profiles and enhance the header names then. @Twan: would probably be good after all to have a GUI element to change that name - we need to think about this, because I remember that we did away with it in the past because it was too confusing, so we need to make it clear what it means.

I have created #206 for this

[dietuyt]

Duplicate of ​http://trac.clarin.eu/ticket/197