You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Suggested by Menzo: the status of a component or profile may change over time, even though the contents remain the same. Perhaps one should be allowed to edit (aspects of) the header (description, group, probably not title) of one's published profiles and components to reflect such changes even after the 'cool down' period.
The Header/Name? element of a component specification is not tied to the name of the root CMD_Component. So we could for example 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">
At this moment this can only be achieved through the ComponentRegistry admin area. We could however extend the UI to allow users to specify a 'friendly name' themselves.
We have to be careful not to make this confusing, since it easily could be to users that are not familiar with the above XML structure. A possibility is to make the 'friendly' name an 'advanced' option, which is initially hidden. Alternatively, the friendly name could be the visible one with the component name being derived from it. An advantage of this is that it would probably decrease the number of 'derived' components with impractical/unpretty names (Session_XYZ) for the XML elements.
The text was updated successfully, but these errors were encountered:
https://trac.clarin.eu/ticket/138
Also relates to https://trac.clarin.eu/ticket/206:
The text was updated successfully, but these errors were encountered: