Skip to content
New issue

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

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

Already on GitHub? # to your account

Use Case L2: Query if a work is available #16

Closed
jonathanrobie opened this issue Apr 4, 2016 · 2 comments
Closed

Use Case L2: Query if a work is available #16

jonathanrobie opened this issue Apr 4, 2016 · 2 comments

Comments

@jonathanrobie
Copy link
Contributor

Some questions about https://github.com/distributed-text-services/API/blob/master/userstories.csv#L2

  • how does the user identify a work? Two approaches seem equally useful:
    • navigationally: 'list all works', select a specific work based on metadata
    • based on a known name or identifier
  • what does the user get when they "retrieve a work"? what is a "work"?
    • metadata describing an edition?
    • the edition itself?
  • Do all searches return collections of 'descriptions', or do searches with unique results simply return the result?
@jonathanrobie jonathanrobie changed the title Use Case: Query if a work is available - https://github.com/distributed-text-services/API/blob/master/userstories.csv#L2 Use Case L2: Query if a work is available Apr 4, 2016
@jeffreycwitt
Copy link

Regarding the second bullet point: "What is a work" and what "metadata" should be returned.

Because the CTS model identifies Version with FRBR Expression but makes no mention of a FRBR Manifestation, you might expect a Work to return a list of available "Versions". But I think Versions should be identified with FRBR Manifestations and Expressions should be reserved for a concept between Works and Versions/Manifestations. See my use case #18

Thus I would like to see a Work return the following properties

  • type=work
  • label
    • e.g. Adam Wodeham Ordinatio, Moby Dick
      description
  • author
  • workType (available workTypes should be determined by the available workTypes specified by the WorkGroupType)
    • e.g. Novel
    • e.g. SentencesCommentary
    • e.g. BiblicalCommentary
      citation
    • e.g Epic Poem
  • hasExpression
  • hasCanonicalExpression
    • since there can be more than one expression, I would like to know which expression is privileged as the default expression to use.
  • hasCanonicalTranscription
    • since there might be a lot of levels between an abstract work and a canonicalTranscription of that work, I would like to see the Work list a privileged transcription that client can default to.

BTW: I tried to provide an answer to the kind of metadata I would like to see accompany each CTS/FRBR resource. My working list is here https://github.com/jeffreycwitt/scta-ontology/blob/master/SCTAOntologySpec.md

@PonteIneptique
Copy link
Member

For cleaning reason, we are closing old issues.
Please feel free to comment if you think we should reopen.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants