Date
Attendees
please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!
Discussion items
| Notetaker? | thank you, Ann Kardos Jennifer Eustis | |
| Product Council Update | This morning's meeting was spent on a presentation to request to build a community of builders. The testing has been product owners. The idea is to have a crowd sourced testing community. They are looking for manual testing to find bugs before releases. They would like anyone to volunteer for testing for up to a year. This includes testing integrations, APIs, etc. They are searching to have names by mid-August to get the testers trained for the upcoming release of Daisy. The capacity planning resulted in new fields in JIRA. They are trying to better reflect issues that have come up in relation especially in reporting. This work is going well around capacity planning. There was a debrief on the stakeholders meeting in Germany. There was MVP planning, state of the budget, resources, need for documentation. A group will be formed to discuss sustainable business models. WOLFCON has designated the official open foundation projects. There might also be a need for informal meetings. The dates for WOLFCON are out 1/20-24 in 2020. This might overlap with ALA MidWinter. | |
| Subgroup Updates and Other Updates | We had talked a couple of weeks ago about new features a regular part of these meetings. Charlotte sent out 2 messages this morning. These are now on the agenda, see below. This will be added going forward. If you didn't get the messages, make sure you are subscribed to the Metadata Management mailing list. Subgroup: Data Import: The small group is not meeting right now. Ann Marie has been working through the comments on the default MARC Bib-Inventory Instance mapping to have it finished by the end of next week. Data Export: This is in the early stage of gathering requirements. A subgroup would be beneficial with about 5-6 people that meets weekly. If you are interested, contact Laura. The subgroup should be diverse. As we discussed in batch editing, if we have only basic features on day 1, good export and import features are needed. | |
| Feature ranking/new features | From Charlotte: We have split UXPROD-1420 "Cleanup work on the Instance Record + look up feature, and new component" into six features, and we'll need the libraries to rank each feature: UXPROD-1889 Instance: Delete warning when deleting format or contributor type UXPROD-1890 Instance: Additional controlled vocabularies for Instance menus UXPROD-1891 Instance: Lookup by code (contributor type, resource type and format) UXPROD-1892 Instance: Add related instances data element UXPROD-1893 Instance: Implement preceding and succeeding titles UXPROD-1894 Settings > Inventory > Instance: Implement format category We have split UXPROD-1880 "Cleanup work on the Item Record" into three features, and we'll need the libraries to rank each feature: UXPROD-1922 Item. Easy copy of barcode and make barcode a link in item list UXPROD-1923 Settings > Inventory > Item: Implement material type category UXPROD-1924 Item. Copy is not a repeatable element Please take a look, and add your institutions new ranking of each of the features above. | |
| SRS/Inventory Freeze | https://folio-project.slack.com/archives/C20V5L40P/p1563288904116100 For clarification, all but a few administrative metadata fields are now "frozen" in the Instance record when there is an underlying source record. The freeze has been enacted. If there is source data underlying an instance record, several records are locked for editing. This applies to any underlying source record. Right now, these are only MARC. | |
| MARC creation and editing needs survey | Laura E Daniels | If you are not using MARC, please note this as well. If you haven't filled this out, please fill this out. This will help with ranking and prioritization. |
| Batch Editing Use Cases follow-ups | https://docs.google.com/spreadsheets/d/1VTRg7CmF_UeZOqp62NVAhDsmqNn4-fqL4N-aH4phSx0/edit#gid=0 | |
Multiple Graphical Representations | Laura, Christie, and Jacquie(?) will be meeting with Tech Council August 7 to discuss this working document: https://docs.google.com/document/d/1e6zlt7Gsd50W1HsRWWM6aerClXYe1l7XACaInVuWcoE/edit Problems:
Functional requirement: Create an instance record and be able to have multiple graphical representations of the language, or be able to put a non-transliterated title that can be searched in other scripts. Note: Charlotte has added following feature description (UXPROD) in Jira: UXPROD-1646 - Getting issue details... STATUS Christie expressed hesitation about being too prescriptive about what the JSON should look like. She suggested spending time on the Functional Requirements. Suggestions for additional functional requirements were added to the Google doc: DRAFT - Multiple graphical representations in FOLIO. (Also linked above.) The group also would like to make recommendations as to what this should look like in the FOLIO interface. Example systems that work well? | |
| Future meeting topics | Source of truth (SRS). Review the FOLIO metadata flow based on test of the newly implementation of edit freeze of records in Inventory when having only SRS and Inventory installed. Is the freeze to happen between SRS and Inventory, or freeze of Inventory is only when there is a MARCcat equivalent of the Inventory record? Rename the Notes accordion in Instance, Holdings, Item and Container record to be renamed, in order to distinguish between the new Notes app (https://docs.google.com/presentation/d/1BMitl09O4C_cg2cN34T5ofZ88Xg3ub3RysDfS6Vue20/edit#slide=id.p) and the notes we have in the metadata records. Inventory Permissions ( UXPROD-1371 - Getting issue details... STATUS ) Search enhancements - possible also look at more general requirements for defining search, e.g. when to use: Phrase search, Truncating (left and/or right), Stemming, Nested search, Boolean search, etc. (TC and MM task) Authority Data and Inventory Vision (small group work first) Discovery – need to clarify sources of data for discovery vs. data needed for operations; this needs to be documented for the entire FOLIO community and direction should come from Product Counil Item record statuses and the apps that affect them Music / Maps / Media cataloging review of data elements in Inventory Felix (via chat) "@charlotte: I could ask a colleague (from one of the 180 network libraries) if she/he could review the beta elements from a 'musical' point of view." Texas A&M may have a music cataloger that can help. Christie offered to load cartographic and music data from other libraries into their test FOLIO instance. Jennifer (via chat): We should also look at video as well. Videos have other standard numbers EAN for instance and fields that people like to search and discovery them by https://wiki.folio.org/pages/viewpage.action?pageId=78336464 |
present? | Name | Organization |
|---|---|---|
| Aaron Trehub | Auburn | |
| Alice Krim | ||
| Ann-Marie Breaux | EBSCO | |
| Ann Kardos | UMass Amherst | |
| Charlotte Whitt | Index Data | |
| Christie Thomas | Chicago | |
| Colin Van Alstine | Smith (FC) | |
| Damian Biagi | ||
| Dennis Bridges | Stacks | |
| Dennis Christman | Duke University | |
| Dracine Hodges | Duke University | |
| ZBW | ||
| Filip Jakobsen | ||
| Jacquie Samples | Duke University | |
| Jason Kovari | Cornell | |
| Jenn Colt | Cornell | |
| Jennifer Eustis | UMass Amherst | |
| Jessica Janecki | Duke University | |
| Kristen Wilson | Index Data | |
| x | Laura Wright | Cornell |
| Lisa Furubotten | Texas A&M | |
| Lisa McColl | Lehigh University | |
| Lisa Sjögren | Chalmers | |
| Lynn Whittenberger | ||
| Martina Schildt | VZG | |
| Mary Alexander | Univ. of Alabama | |
| Nancy Lorimer | Stanford | |
| Natascha Owens | Chicago | |
| Niels Erik Nielsen | ||
| Patty Wanninger | EBSCO | |
| Former user (Deleted) | HeBIS-Verbundzentrale | |
| Sara Colglazier | MHC/5C | |
| Sarah Ross | Cornell | |
| Sarah Schmidt | Duke University | |
| x | Tiziana Possemato | |
Theodor Tolstoy | EBSCO | |
| Wayne Schneider | Index Data |