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

Field to enter volume/part on editions #2452

Open
BrittanyBunk opened this issue Oct 3, 2019 · 7 comments
Open

Field to enter volume/part on editions #2452

BrittanyBunk opened this issue Oct 3, 2019 · 7 comments
Labels
Affects: Data Issues that affect book/author metadata or user/account data. [managed] Lead: @seabelis Issuses overseen by Lisa (Staff: Lead Community Librarian) [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] Type: Subtask of Epic A subtask that is part of the work breakdown of an epic issue (see comments). [managed]

Comments

@BrittanyBunk
Copy link
Contributor

Just like how there's a place to write 'name of edition' - like 1st edition, there should be a box to say 'name of volume or part' to say volume 1, or part 5 or something.

@BrittanyBunk BrittanyBunk added the Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] label Oct 3, 2019
@LeadSongDog
Copy link

It is not just a box that's needed: the schema has no data fields to support identification of sequential elements (such as issues and numbers of a serial, volumes of a multivolume edition, or books of a multi-book work). This is a huge, ugly gap that has been with us for many years. Perhaps as it becomes possible to consider schema changes this could be treated as one of the more important ones to address.

@mekarpeles
Copy link
Member

@LeadSongDog do we have an epic (overarching) issue for this? If so, would you be able/willing to post it here? I'm happy to add the epic label to it so we can keep volume/serial related efforts connected.

@mekarpeles mekarpeles added the Type: Subtask of Epic A subtask that is part of the work breakdown of an epic issue (see comments). [managed] label Oct 3, 2019
@LeadSongDog
Copy link

@mekarpeles
#561 addressed much of it, perhaps that should be tagged epic?

@BrittanyBunk
Copy link
Contributor Author

what if it's volume/series/part?

@xayhewalo xayhewalo added Affects: Data Issues that affect book/author metadata or user/account data. [managed] Priority: 3 Issues that we can consider at our leisure. [managed] State: Backlogged Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Nov 17, 2019
@xayhewalo
Copy link
Collaborator

@mekarpeles what's the parent epic for this issue?

@BrittanyBunk
Copy link
Contributor Author

@guyjeangilles I think it relates to #1808

@BrittanyBunk
Copy link
Contributor Author

I'm adding onto this by saying, in addition to edition, there should be a place to write in the version (type of book - so 1st edition in paperback, another in hardcover, another in audiobook, etc.).

@hornc hornc changed the title Box to enter volume/part Field to enter volume/part on editions Jan 8, 2020
@mekarpeles mekarpeles removed the Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] label Apr 20, 2020
@mekarpeles mekarpeles added Lead: @seabelis Issuses overseen by Lisa (Staff: Lead Community Librarian) [managed] and removed Needs: Lead labels May 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: Data Issues that affect book/author metadata or user/account data. [managed] Lead: @seabelis Issuses overseen by Lisa (Staff: Lead Community Librarian) [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] Type: Subtask of Epic A subtask that is part of the work breakdown of an epic issue (see comments). [managed]
Projects
None yet
Development

No branches or pull requests

5 participants