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

Identify Base SUDOC call numbers #406

Closed
1 task
banukutlu opened this issue Apr 11, 2022 · 0 comments · Fixed by #507
Closed
1 task

Identify Base SUDOC call numbers #406

banukutlu opened this issue Apr 11, 2022 · 0 comments · Fixed by #507
Assignees
Milestone

Comments

@banukutlu
Copy link
Contributor

banukutlu commented Apr 11, 2022

Part of #285

In SUDOC, we can expect letters and numbers separated by one of: :-./ and possibly spaces. However, there MAY not be a space before the parts information, e.g.

  • D 101.47:v.14
  • C 3.2:H 62/8/v.2

These would be after the last separator of some kind, however.

We should expect the most common volume, issue, and number, v. iss. vol. num. etc words and we only expect English on these.

Also, if we are removing things like "KIT" from call numbers, we will want to bring that over here, e.g..

  • HE 20.427:C 76/2/KIT.
  • HE 20.427:H 33
  • HE 20.427:H 75/PACK.
  • HE 20.427:IL 6/KIT
  • HE 20.427:IN 7

WDLL

  • Generate base call numbers for SUDOC call numbers
@banukutlu banukutlu added this to the 1.1.x milestone Apr 11, 2022
@banukutlu banukutlu changed the title Handle SUDOC call numbers Identify Base SUDOC call numbers Apr 11, 2022
@banukutlu banukutlu modified the milestones: 1.1.x, 1.2.x May 18, 2022
@ajkiessl ajkiessl self-assigned this May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants