Skip to main content

Notice

The new RDA web platform is still being rolled out. Existing RDA members PLEASE REACTIVATE YOUR ACCOUNT using this link: https://rda-login.wicketcloud.com/users/confirmation. Please report bugs, broken links and provide your feedback using the UserSnap tool on the bottom right corner of each page. Stay updated about the web site milestones at https://www.rd-alliance.org/rda-web-platform-upcoming-features-and-functionalities/.

Requirements and use cases for the DFT term gathering application

  • Creator
    Discussion
  • #138774

    Raphael Ritz
    Participant

    A collection of features that we need or want in order to support the WG’s term gathering effort.

    Access policy

    A1. No anonymous contributions -> login feature required

    A2. Traceable user source -> authentication against RDA user base preferred (required?)

    A3. We work fully in the open -> no private areas/pages required
     

    Content policy

    C1. Everyone should be able to suggest terms -> everyone needs “add content” privileges

    C2. Collaborative editing (do we want that?) -> if so, everyone needs “edit content” privileges

    C3. Term pages should be structured in an agreed upon way. If we want to enforce that we need the add/edit forms to reflect that

    C4. Commenting (either in text or dedicated) -> obvious way to add comments required

    Further features

    F1. Discoverability of recent additions and changes -> email notifications or timeline or watching/staring required
       (RR: do we insist on email notifications or is that rather considered noise?)
     
    F2. Versioning/revision log/diff views — do we want or need that? (RR: at the very least a “nice to have”)

    F3. Categorization — do we want or need to be able to tag or categorize content?

    F4. Relations — do we want or need to be able to establish (typed?) relations between pages/terms?

    F5. Voting — do we need a way beyond comments for people to express (dis)agreement?

    Sustainability

    S1. Content export -> certainly nice to have but do we require that? (and if so in what format and to what level of detail?)

    S2. Open source code base -> in the spirit of RDA this would be appreciated but should we require that?

    S3. Ease of administration and deployment
     

    related: candidate applications

Log in to reply.