2017-10-19 Metadata Management Meeting Notes

Product Council Update

@Former user (Deleted)

The PC had a few guests at today's meeting. These are people helping with a revamp of the FOLIO website. They did a small demo using wireframes. They showed how the website is being reorganized to address the various audiences that may be interested in FOLIO. Dracine guesses the website relaunch will be in the next few months. A new FOLIO logo will be debuted at next week's meeting. There is a call for FOLIO presentations at NASIG. If anyone is interested, please reach out to @Rachel Fadlon, EBSCO representative. The NASIG conference will be in Atlanta in June of this year. http://www.nasig.org/site_page.cfm?pk_association_webpage_menu=700

Any updates from the Forum Facilitators or Linked Data WG?

 @jdolivarez had no updates.

Holdings & Instance mapping working groups

• The Instance metadata MARC mapping workgroup will meet on Monday 10/23 - wiki page https://folio-org.atlassian.net/wiki/display/MM/Instance+MARC+mapping+working+group

• The Holdings data/MARC mapping working group will meet on Wednesday 10/25 - wiki page https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=4653565

@Cult Cataloguing Module demo

@Charlotte Whitt

Tiziana Possemato

Tiziana demonstrated the cataloging module from AMICUS. Features demonstrated:

• Cataloging Starting Places:

  • Templates for original cataloging

  • External database sources

  • Loading from a file

• Searches

  • There are more than 400 indexes for searching bibliographic, authority, or holding records, as well as inventory.

  • Holdings contain data related to the copy (i.e. barcodes, circulation rules)

  • Inventory contain data related to Acquisition information.

• Views

  • Libraries can define "views" that highlight different aspects of the same record.

• Example Search: ti harry potter (This will give all of the records in which Harry Potter is included.) Scan gives a results list.

  • Result screen:

    • NT: Indicates a name/title access point is available

    • Refs: Cross reference

    • A: Authority Heading

    • Docs:

    • Level:

    • Index: Language of cataloging

• From the results screen a headings list can be derrived, and those headings can be search

• Example Search 2: na kafka

  • Result screen:

    • From here URI associations from various sources can be made. (Sources: VIAF, LOC authorities, ISNI). The URI can be added to the record right from the cataloging interface. The URI can be added into the record.

• Example Search 3: na rowling, j.k.

  • Results screen:

    • Two headings for the same person are displayed. From this screen, the correct heading can be transferred to overlay the incorrect one.

    • Also, the name/title groupings can

• Example Search 4: ntn rowling, j.k.

  • Results screen:

    • A new name/title heading can be created from the results. The authoritative name can be related to the title.

• Load from VIAF

  • From this screen, a new authority record can be loaded from an external source like VIAF. The record is then imported into the local database.

  • The detailed parts from the VIAF authority record can be selected for what is useful to your system. See also references can be limited to the language useful to your library if necessary, for example.

• External searching for bib records

  • The system can be configured to search other databases. It uses Z39.50, or can search by API. OCLC can be added for this search.

• Upload from file

  • Input methods:

    • "Load server mode"

    • "Overwrite record"

  • Example: MARC record loaded. MARC 21,UNIMRC, ONIX 3.0 are uploadable formats.

  • A list of records that are in the upload record file is displayed by the system.

• New record

  • A list of templates are given.

  • They are working to be able to work in RDA. At this point the workflow originates with MARC 21 formatting.

  • Authoritative forms of name headings can be called up from VIAF or other authority file into the cataloging record.

  • RDA tags are available for selection.

  • A list of standard, frequently used notes can be created and drawn from during this process.

  • A new name heading can be created if it is not available from an external authority file.

  • Record can be derrived from other existing records in the catalog.

  • A relationship can be created as well, that will relate a print to an electronic item, for example.

  • All MARC21 defined relationships can be established.

  • A digital ??? Access ele

• FRBR relationships can be established. Entities: Works and Manifestations can be defined in the system.

• Work authority records can be found from external sources and imported.

If you have questions about this product, please send them to the MM SIG mailing list (metadata-mgmt-sig@ole-lists.openlibraryfoundation.org). Lynn will compile the questions and forward them to Tiziana herself. Lynn will then post the answers on the discuss forum.