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.

Sign up for GitHub

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

Jump to bottom

Potential Fields to Add to the MARC Bot #9916

Open
JordanFrederick opened this issue Sep 28, 2024 · 0 comments
Open

Potential Fields to Add to the MARC Bot #9916

JordanFrederick opened this issue Sep 28, 2024 · 0 comments
Labels
Lead: @scottbarnes Issues overseen by Scott (Community Imports) Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]

Comments

@JordanFrederick
Copy link

Proposal

As I discussed with @scottbarnes, I believe the MARC Bot could benefit from the following fields:

247: Former Title (when relevant)
306: Playing Time (for audiobooks)
341: Accessibility Content - subfields $b (Textual assistive features), $c (Visual assistive features), and $d (Auditory assistive features), in particular
370: Associated Place - subfield $c (Associated country)

@hornc, @tfmorris. I'm open to discussing further.

Justification

Breakdown

Requirements Checklist

  • [ ]

Related files

Stakeholders

Instructions for Contributors

Please run these commands to ensure your repository is up to date before creating a new branch to work on this issue and each time after pushing code to Github, because the pre-commit bot may add commits to your PRs upstream.
@JordanFrederick JordanFrederick added Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed] labels Sep 28, 2024
@mekarpeles mekarpeles added Lead: @scottbarnes Issues overseen by Scott (Community Imports) Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed] and removed Needs: Lead Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Lead: @scottbarnes Issues overseen by Scott (Community Imports) Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Priority: 4 An issue, but should be worked on when no other pressing work can be done. [managed] Type: Feature Request Issue describes a feature or enhancement we'd like to implement. [managed]
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mekarpeles @JordanFrederick