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

Greek and Modern Greek are both included on edit form. #8145

Closed
seabelis opened this issue Jul 31, 2023 · 6 comments
Closed

Greek and Modern Greek are both included on edit form. #8145

seabelis opened this issue Jul 31, 2023 · 6 comments
Labels
Affects: Data Issues that affect book/author metadata or user/account data. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Type: Bug Something isn't working. [managed]

Comments

@seabelis
Copy link
Collaborator

Both Greek and Modern Greek are languages on the edition edit form. I do not see there is a different language code for just "Greek." This may be an error. Additionally, many titles that were probably imported as Ancient Greek, have Modern Greek identified as the language. There may have been some import issues early on that mixed up the codes.

Evidence / Screenshot (if possible)

Screenshot 2023-07-31 at 12 19 25 Screenshot 2023-07-31 at 12 19 17

Relevant url?

Steps to Reproduce

  1. Go to ...edition edit form.
  2. Do ... check for greek and modern greek.
  • Actual: Both exist.
  • Expected: Greek should probably not exist. Modern Greek should probably be listed as Greek, Modern.

Details

  • Logged in (Y/N)?
  • Browser type/version?
  • Operating system?
  • Environment (prod/dev/local)? prod

Proposal & Constraints

Related files

Stakeholders

@seabelis seabelis added Type: Bug Something isn't working. [managed] Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Affects: Data Issues that affect book/author metadata or user/account data. [managed] Needs: Lead labels Jul 31, 2023
@tfmorris
Copy link
Contributor

This is likely because https://openlibrary.org/languages/gre.yml has both a name of "Greek" and a name_translated.en of "Modern Greek". If I'm right, choosing either will result in a language code of gre.

#8138 is related. There are no non-English labels for "Ancient Greek" available at all. When those are added, they are going to use normal name order, as is the custom on Wikidata. I personally think that is the right way to do it and think the English label should also use normal name order as well, as it has since 2009 (which, of course, means that the autocomplete widget can't be restricted to prefix searches as it currently appears to be).

Additionally, many titles that were probably imported as Ancient Greek, have Modern Greek identified as the language. There may have been some import issues early on that mixed up the codes.

Do you have some examples of these import errors? I'd be happy to investigate. The first potential example I checked was imported from a Scriblio MARC record (mis)coded as gre and had grc added later by "MARC Bot" (without any provenance) which is the opposite of the problem you're describing.
https://openlibrary.org/books/OL6984687M/Magni_Hippocratis_Coi_opera_omnia.?b=8&a=7&_compare=Comparer&m=diff

@seabelis
Copy link
Collaborator Author

Thanks, @tfmorris . I'll post the next example I run across.

I do not object to listing Ancient Greek in normal order, but as you mention, the auto-complete should then be able to find it as an option when someone types "greek".

@tfmorris
Copy link
Contributor

@seabelis I've created #8146 to cover fixing this.

@cdrini cdrini added Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] and removed Needs: Lead labels Jul 31, 2023
@seabelis
Copy link
Collaborator Author

seabelis commented Aug 2, 2023

@tfmorris https://openlibrary.org/books/OL24990264M/Republic_of_Plato?v=1 Created from an import from archive.org where the book is cataloged as just Greek.

@tfmorris
Copy link
Contributor

tfmorris commented Aug 2, 2023

@seabelis Thanks for the example. Sorry to say that there's not enough provenance to figure out what code imported that record. I had a look at the import code as it existed around that date and didn't see anything obvious which would have caused the problem. I can only assume that something intentionally remapped gre to grc as part of the import.

This is another thing which would presumably get fixed if a run was doing re-importing all MARC records with the current improved MARC parser and import pipeline.

@cdrini cdrini added Priority: 3 Issues that we can consider at our leisure. [managed] and removed Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] labels Nov 20, 2023
@cdrini
Copy link
Collaborator

cdrini commented Aug 19, 2024

Fixed by #8160 .
image

@cdrini cdrini closed this as completed Aug 19, 2024
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: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Priority: 3 Issues that we can consider at our leisure. [managed] Type: Bug Something isn't working. [managed]
Projects
None yet
Development

No branches or pull requests

3 participants