3 of 12

Why else do catalogers want this feature? Quotes from them... cont’d

Author browsing is especially helpful for troubleshooting when a known-item search fails: "Why is this known item not being collocated with other resources by the same author?" An author browse undertaken in the service of troubleshooting and other quality-control tasks is a valuable means of identifying cataloging errors that need to be corrected.

I want to be able to type in an author's last name and some part of the first name to see what form(s)are used in our catalog. In addition to correcting errors (see Tim's point above), this can be very helpful in cataloging, when deciding which of several possibilities is the correct author. I want to be able to see titles associated with each author, either in the initial search result or by clicking on the author, so that I can see the subject area for that author.

| www.folio.org

4 of 12

Why else do catalogers want this feature? Quotes from them...

Browsing by author is especially important for classification of works in the M, N, and P schedules, where authors (and artists and composers) are assigned a custom class and/or extending cutter number that serves as their home address, as it were. An author browse is a starting point for several decisions when cataloging such works. First, it helps a cataloger quickly determine what titles we already hold, if any, and how they have been classed in our local catalog. It's also a shortcut into the appropriate range of the schedules, without having to scroll through the entire M or P schedules in ClassWeb. Finally, it's a way to identify creators who still need literary or artistic numbers established, and where they should slot in alphabetically.

| www.folio.org

5 of 12

Live example - https://catalog.lib.uchicago.edu/vufind/Alphabrowse/Home?source=author

Enter Dickens, Charles

| www.folio.org

6 of 12

Mikhail’s questions

Q1. What will be the ultimate final solution, in which authority contributors will be matched to instance contributors?

A1. Ultimate solution - The cataloger will have two options a.) manually link the authority contributor to the instance contributor. The link will autopopulate the instance contributor with the authority heading value (personalName, corporateName, conferenceName heading type) and we will define a match point. b.) Via quickMARC bib record there will be an option that allows the user to do an automatic matching of authority heading to applicable instance contributor MARC field. We need to work out if we will support exact match only or near match.

Q2. Will they be shown in one result list, in which some of the rows are from authority, that are matched to the instances, some are not matched, and some are from instance contributors?

A2. Yes, for the Browse contributors results list the user will be able to browse authorized contributors (meaning contributors linked to an authority heading record) AND ALSO view on the same list unauthorized contributors (meaning contributors only stored on the instance record AND not linked to an authority heading record). This Browse list will show an indicator so the user knows which results are linked to an authority heading record. Also on the Instance record, each contributor row under the Contributors' section will also show an indicator that it is linked to an authority heading. NOTE: That what I have outlined regarding the link between an authority heading and instance/bib records is out of scope for this feature. It is Phase 2 and when considering Phase 2, we will need to support the same treatment for the Subject browse implementation.

| www.folio.org

7 of 12

Mikhail’s questions cont’d

Q3. Another one small question is whether the size of one page of results be e.g. 25? (It is essential for performance of one of the approaches)

A3. No change from previous browse UX. We will display 100 results maximum per page. The anchor result will be the 6th result on the list (whether returned or not) and a user should be able to browse the entire list of contributors by the use of Previous and Next navigation.

| www.folio.org

8 of 12

Proposed high level requirements

Backend : implement browse contributors support in mod-search
See Subjects browse (back-end feature) as is it closest to what we need to implement to support contributors https://issues.folio.org/browse/UXPROD-3447
The browse list should display preceding, matching and succeeding contributors
Browse by Contributor's name value
Contributors should be ordered in the alphabetical order
Highlight anchor result
Pagination: The user should be able to navigate the contributors' browse list forward and backward
Response should also return Name type AND type values too

| www.folio.org

9 of 12

Proposed high level requirements cont’d

Browse must support returning the number of instance records that is an exact match to the Contributor's name value
Clicking on the # of instance records should conduct a search for all instances that include the contributor
Must support placeholder for missing match
Can view implementation on Inventory app > Instance search toggle > select Browse subjects option - https://bugfest-lotus.int.aws.folio.org/inventory?filters=&sort=title

| www.folio.org

10 of 12

Browse contributors

User will have the ability to browse by the contributor named entered/populated on an instance record.

| www.folio.org

11 of 12

Browse contributors

This example shows when the query entered is not found.

A placeholder row displays
Clicking on a row that is not a placeholder will kick off an instance search

| www.folio.org

12 of 12

Browse contributors

This example shows when the query entered is found.

If a match is found then it is highlighted in a bold font

| www.folio.org