Filip Jakobsen, Annalisa Di Sabato, Tiziana Possemato

@Cult will do a write up of the out standing questions, and send out to the group to get feedback and discuss all together during this meeting.

Tiziana shared the screen displaying the UX design proposed.

1. Search & Filtering

• • Tiziana reviewed her understanding of the requested functionality and confirmed that MARCCat can be designed to accommodate these features.
  • Do we want a "fixed filter" or a "sensitive" filter?
  • Format type:
  • Method: Each topic gets its own page, to which the group can contribute feedback.

______________________________

?????? What do we want in the drop downs?

• • Subject
  • Begins with

____________________________________

Do you prefer to have a fixed filter, or sensitive filter - one that changes based on format selected.

Sarah - Do not need right away

____________________

What headlines should display? What options should show under these? Truncated with ability to open to see more? On this screen we're seeing just placeholders, this needs to be thought out.

___________________________________

2. Screen 2

Locating duplicate records in the system. If one of the filters in the search/filter pain could help identify duplicates. the dropdown showing at the bottom, if all of the fields meet those conditions ("and") then the duplicates will display. The idea of this, in combination with batch editing, duplicate records would be able to be located, then resolved in whatever way.

Tiziana? - Is it possible to have and example? Lisa will send an example. Tiziana is looking for clarity on what is wanted. Sarah pointed out that this is a lower priority.

____________________________________________________________________

Screen 3: Library wide defined, not at the user level. Agreed it should function this way.

_____________________________________________________________

Screen 4: No questions/issues

_______________________________________

Screen 5: Is it necessary to have the ability to apply this sophisticated logic - one that is applied to Fixed Field and positional tags. How important is this? If yes, then @Cult needs a list of possible tags.

This comes into play when verifying headings.

"Not necessary for version 1, but very nice to have. Nice to come back to - do not focus on at this point.."

_________________________________________

Screen 6: Do you want to search and retrieve both authority and bibliographic records, using specific filter? Answer: This is already in the UI. The check boxes and filters are already available.

Screen 7: Is this enough information?

1. More discussion is needed about this "Heading" Function.

Screen 8: Tiziana will ask Filip about this on Monday.

Do we want to display the bib fields in the results? There are times, for example when searching through everything, that the bib field may not be as obvious as this example.

Do the Bib fields need to display in the 2nd pane? Chicago and Jacquie - We don't need to see the bib fields in the brief results. What is showing is sufficient.