Skip to end of banner
Go to start of banner

2019-08-15 Metadata Management Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date

please put an 'x' next to your name in the list below the "Discussion items" if you are attending. Thanks!

Discussion items

Product Council Update


Subgroup Updates and Other Updates


Feature ranking/new features?

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 should not be a repeatable element

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

PO-MVP/MVP and Capacity Planning updateLaura E DanielsInventory features - CWFeaturesByEpic
Search in Inventory update, mock-upCharlotte WhittSlide deck - Search in Inventory - UXPROD-140 (Misc. UX) –  (smile) and not completely done (time was running too fast)

Multiple Graphical Representations

Laura, Christie, and Jacquie met with Tech Council Aug. 7 – still some work to be done around ideal display options and sample data

working document:

https://docs.google.com/document/d/1e6zlt7Gsd50W1HsRWWM6aerClXYe1l7XACaInVuWcoE/edit

Problems:

  • If multiple forms of the value are represented in a single JSON object, both scripts have to be included in a single value cell. This limits the search function.
  • Chicago is testing graphical representation in FOLIO. Here is an example:

  • See MARC record: https://catalog.lib.uchicago.edu/vufind/Record/8539712/Details#tabnav
  • See JSON sample: (Christie will provide)
  • Functional requirements need to be built so developers can understand the issues. What would we like to have happen in FOLIO?
  • Proposed solution:
    • Single JSON object for the property, e.g., Title, with the ability to have an array of values for display (labels).

    • Values should allow for a property that identifies the script.

    • This would allow for the ability to configure displays to include multiple representations or a selection of representations.

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: 

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.



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.

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 ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

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 TrehubAuburn
      Alice Krim

Ann-Marie BreauxEBSCO

Ann KardosUMass Amherst


Charlotte WhittIndex Data

Christie ThomasChicago

Colin Van AlstineSmith (FC)

Damian Biagi

Dennis BridgesStacks

Dennis ChristmanDuke University

Dracine HodgesDuke University

ZBW

Filip Jakobsen

Jacquie SamplesDuke University

Jason KovariCornell

Jenn ColtCornell

Jennifer EustisUMass Amherst

Jessica JaneckiDuke University

Kristen WilsonIndex Data
xLaura WrightCornell

Lisa FurubottenTexas A&M

Lisa McCollLehigh University

Lisa SjögrenChalmers

Lynn Whittenberger

Martina Schildt

VZG


Mary AlexanderUniv. of Alabama

Nancy Lorimer

Stanford


Natascha OwensChicago

Niels Erik Nielsen

Patty WanningerEBSCO

Former user (Deleted)HeBIS-Verbundzentrale

Sara ColglazierMHC/5C

Sarah RossCornell

Sarah SchmidtDuke University

Tiziana Possemato

Theodor Tolstoy

EBSCO

Wayne Schneider

Index Data

  • No labels