Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Description (header) of published profiles should be editable #47

Open
twagoo opened this issue Jul 20, 2016 · 0 comments
Open

Description (header) of published profiles should be editable #47

twagoo opened this issue Jul 20, 2016 · 0 comments
Milestone

Comments

@twagoo
Copy link
Member

twagoo commented Jul 20, 2016

https://trac.clarin.eu/ticket/138

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.

Also relates to https://trac.clarin.eu/ticket/206:

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.

@twagoo twagoo added this to the 2.3.0 milestone Jul 20, 2016
@twagoo twagoo modified the milestones: 2.3.0, 2.4.0 Nov 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant