Note: A recording of each week's meeting can be found in the following Google Drive folder: https://drive.google.com/drive/folders/0B7G8S7WF6N20YUM4My1oRTIxSHM
Discussion items
Item
Who
Notes
Product Council update
No updates for today.
Subgroup updates
Lynn/Charlotte: Advanced searching |
Resource/Format - A 4th meeting is being scheduled. Members are being contacted.
Christie Thomas has agreed to serve on a FOLIO tags subgroup.
Sarah from Duke is participating on the Special Collections subgroup. She will report
Felix Hemme will participate on the ERM subgroup. On March 21 and 22 there will be a two day meeting.
Data Migration Group
Wayne and Charlotte are participating in a data migration subgroup. They are working with the German group of libraries to migrate their data.
Christie is working with Dale at Chicago to migrate their data into a FOLIO Alpha instance. Is it worth having another subgroup meeting for those who are working on mapping. They are finding elements that are not being represented. Charlotte suggested reconvening with that working group. Right now the group is working with a long list of missing elements and could use the input from Chicago now.
Ann-Marie asked how the batch MARC loader discussions are progressing. Lynn will speak to Filip about this.
What should the timing be on fine-tuning data migrations? Should we focus on Alpha, or wait for a more robust version?
Patty Wanninger said that the migration team is working on a gap analysis. They will consolidate "what is missing" and send it to the Product Council.
Charlotte recommends that we have a conversation about all of the elements defined as "missing" and not wait until later. This could be a smaller group. Christie agreed that if the data-migration group is doing a gap analysis they could take part now.
Jacquie asked whether we need the Product Council's "permission" to do a gap analysis.
Lynn will connect with Patty, Wayne, and Charlotte and figure out how gap analysis can work, then decide our next steps.
Face to Face sessions or Workshop sessions at WOLFcon? (sometime in June)
Charlotte added notes from our last meeting in the spreadsheet. The developers are eager to get this feedback. Charlotte has a meeting with them today and tomorrow about this.
Laura - Would we want to search by edition? Sarah at Duke said that is a common search for rare books and music, and that a combined search for title and edition may be used, as an example.
Publisher - Ann-Marie said that keyword is the important part of this search.
Place of Publication - Right now they are mapping from the 26X field. Jacquie asked whether the fixed field data should be searched in an advanced search, for publisher date and publication place. Wayne - Data from the fixed fields may get converted when going from a MARC record to an inventory record. The fixed field will no longer be a separate element in the data model for the inventory app. Patty - Is there documentation to say where this information is coming from? "Instance Metadata for Inventory" - spreadsheet shows this information. Jacquie - the fixed field data have lookup data in the LC thesauri - may be a better place when consider a linked data environment. Wayne - How do you imagine searching? By code? By a place name as represented in the LC thesaurus. Jacquie - a place name or place code could be used to be searched. Wayne - Does the model need to be expanded to include the place name code from the 008 field? Would the code be separated? Laura Wright would not want to see us get rid of the 26X place of publication.
Publication Date - This should be included in a basic search as well as an advanced search.
URL - 856 information. - Fine for advanced
Resource type - (Equivalent with RDA Content - "Format" is the "media" and "carrier type") - Ann-Marie - Is this something that belongs in a filter?
Filtering vs. Faceting:
Filtering - Predefined list of things of things you apply prior to search
Faceting - A set of things that comes out of a result set that comes from a search.
Wayne - right now all we have are "filters." The interface is designed to work with filters at the moment. Should it be a combination of the two types? Should it be all filters or all facets?
Physical Description - Good for Advanced Search
Language - Drawn from fixed fields and 041 - This is as a filter, even in a basic search. As long as we have a title search with a language filter, that should be fine.
Notes - This refers to the 5XX fields and maybe 310 fields. This will part of the Advanced Search. Keyword search right now is keyword of title, contributors, identifiers, ISSN. Lynn would expect it be a keyword of everything - the entire record.
Date Added to FOLIO - when was record added, and when was it updated. Should it be part of a search? It's a good data point for reporting. Might want to be able to sort by date
Location - Filter/Facet
Holding Call#; truncation is finie - advanced search screen only might not be adequate - would want to search call# from basic screen. WS: if type in full call# in basic search, would you expect to get to the item - YES. So the holding/item call# data needs to be included in the keyword index;
Holdings statement - not needed for basic search; any holdings notes search would be advanced search or reporting
Items barcode: Barcode - should also be searchable from the basic screen - CW: developing dropdown menu to select; should there be autocomplete or exact match - exact match
item temp location: should temp location show up in the "locations" filter? if item has perm & temp location, should filter display both locations? - yes
Enumeration: Not needed for searching at all.
Chronology: Not needed for searching at all.
Piece Identifier (vol. 1, vol. 2 etc): Not needed for searching at all.
Number of Pieces: Not needed for searching at all.
Item Note: This should be in keyword index from basic search. May want to use for advanced search.
Loan Type: May be relevant for circulation staff, but in the Advanced Search.
Item Status: This will be a controlled vocabulary.