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

Librarian-only: Empty brackets after author name #10352

Open
zorae opened this issue Jan 17, 2025 · 4 comments
Open

Librarian-only: Empty brackets after author name #10352

zorae opened this issue Jan 17, 2025 · 4 comments
Labels
Affects: Librarians Issues related to features that librarians particularly need. [managed] Good First Issue Easy issue. Good for newcomers. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Module: Integrated Librarian Environment (ILE Bar) Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Response Issues which require feedback from lead Priority: 3 Issues that we can consider at our leisure. [managed] Type: Bug Something isn't working. [managed]

Comments

@zorae
Copy link

zorae commented Jan 17, 2025

Problem

OL displays the years of birth and death in author links if you are signed in as a librarian. When both fields are empty, this is omitted. But when the fields contain something that no year can be parsed from, an empty pair of brackets with a hyphen is displayed.

Example page where the author’s birth year cannot be parsed because I set it to “19xx” to indicate that she was born in the 20th century.
Image

Reproducing the bug

  1. Go to ...
  2. Do ...
  • Expected behavior:
  • Actual behavior:

Context

  • Browser (Chrome, Safari, Firefox, etc): Safari
  • OS (Windows, Mac, etc):
  • Logged in (Y/N): Y
  • Environment (prod, dev, local): prod

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.
@zorae zorae 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: Bug Something isn't working. [managed] labels Jan 17, 2025
@cdrini cdrini added Priority: 3 Issues that we can consider at our leisure. [managed] Good First Issue Easy issue. Good for newcomers. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Affects: Librarians Issues related to features that librarians particularly need. [managed] Module: Integrated Librarian Environment (ILE Bar) and removed Needs: Triage This issue needs triage. The team needs to decide who should own it, what to do, by when. [managed] Needs: Lead labels Jan 17, 2025
@SharkyBytes
Copy link
Contributor

Hi @zorae,

Could you please help me reproduce this issue? Currently, I’m not signed in as a librarian; I’m using a local user account. Could you provide a reference or guide on how I can sign up or gain librarian access?

Alternatively, if it’s possible to reproduce the issue in a local environment, I do have the admin instance set up there. Any specific instructions or tips would be greatly appreciated!

@Rithvik1709
Copy link

Hey @zorae is this issue active , would love to contribute
thanks

@github-actions github-actions bot added the Needs: Response Issues which require feedback from lead label Jan 18, 2025
@scottbarnes
Copy link
Collaborator

It's possible that copydocs.py and adding local users and changing their usergroups might be helpful here, if one desires to try to replicate this locally.

In terms of creating additional users, step 3 can probably be skipped if one is willing to use http://localhost:8080/admin/people to use the 'login as another user' feature that's available after clicking on a specific account (e.g. your new librarian account).

No idea whether any of this is relevant.

@tfmorris
Copy link
Contributor

There are two related cases where useful author date information is not shown:

  • when there is a death date, but no birth date, nothing is displayed
  • the contents of the freeform date field isn't displayed if the structured birth & death date fields are empty. I don't remember it's name of the top of my head, but it typically contains things like "fl. 14th c." This is a legacy field which is no longer editable, but, if populated, usually contains useful disambiguation information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Affects: Librarians Issues related to features that librarians particularly need. [managed] Good First Issue Easy issue. Good for newcomers. [managed] Lead: @cdrini Issues overseen by Drini (Staff: Team Lead & Solr, Library Explorer, i18n) [managed] Module: Integrated Librarian Environment (ILE Bar) Needs: Breakdown This big issue needs a checklist or subissues to describe a breakdown of work. [managed] Needs: Response Issues which require feedback from lead 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

6 participants