Skip to content
This repository has been archived by the owner on May 7, 2021. It is now read-only.

New CTS Linked Data Publication App #7

Open
balmas opened this issue Jun 9, 2015 · 2 comments
Open

New CTS Linked Data Publication App #7

balmas opened this issue Jun 9, 2015 · 2 comments
Assignees

Comments

@balmas
Copy link
Collaborator

balmas commented Jun 9, 2015

Per perseids-project/perseids_docs#259 and discussion with @annakrohn yesterday, for the Digital Millet workflow we want to create a new Perseids input app which allows a user to create a new CTS-driven linked data publication in Perseids. The app should create a JSON-LD data structure using the OA data model which describes the elements of the publication and supplies the initial values. Subsequent editing of the publication will be through the existing application features in Perseids.

The following data types should be able to be created from this from:

  1. a new Translation of a specific passage or passage range of a canonical work (entered in plain text not XML)
  2. a new Commentary targeting a specific passage or passage range of a canonical work

We also want to be able to specify a keyword or set of keywords and a bibliography, but need to check with @Marie-ClaireBeaulieu about whether these should target the selected CTS passages or the work as a whole, or the linked data publication itself.

Features which might be nice to have but which might be out of scope and need further discussion wrt to the requirements:

  1. the ability to choose whether the commentary targets the translation instead of the canonical text
  2. the ability to enter more than one commentary
  3. the ability to enter more than one translation
  4. the ability to specify an existing translation of the canonical passage
@balmas
Copy link
Collaborator Author

balmas commented Jun 9, 2015

The following should be configurable options for the application and not hardcoded:

  1. the endpoint for creation of the publication

  2. the endpoint for editing after initial creation

  3. the endpoints for the CTS service endpoint (for serving the canonical texts and translations)

  4. the CITE collection to which the commentary item gets added

    a. this may be something we either want to allow the user to specify in advanced options, or to be supplied in the query string so that we can use the app for multiple collections

@Marie-ClaireBeaulieu
Copy link

@balmas @annakrohn : thanks, that's great. My understanding is that the keywords should target the CTS passage. If I hear differently today, will update here. @balmas @annakrohn , after discussing it at the meeting this morning, keywords need to apply to the CTS passage and words within each passage will be tagged too

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants