Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ItemWhoNotes
Product Council UpdateFormer user (Deleted)

Dracine, while not able to attend, emailed Laura that there are no new updates from the Product Council.


Viewing working version of FOLIO - discussion

Main page of the FOLIO page, there is a link to folio-snapshot-stable https://wiki.folio.org/. This is updated nightly.

At the end of September, a fairly stable release will be produced. Laura will let Dracine know that there is a desire to

Subgroup updates

Batch Loader - The developers have an architecture designed that will be review. Latest discussions surround the log, and what information is desired for the log. The screens need to be finalized in 2-3 weeks. The stories need to go to developers by mid-October at the latest

ERM - They began discussing requirements for licenses.

Container Records Working Groups - Met with Filip to discuss how to implement a container record as an object similar to an instance record. They also discussed how to integrate with other apps.

MARCCat - A sub-sub group has met with Filip to develop starting sketches. This was brought to the MARCCat subgroup today, with positive reactions.


Update on UX work for analytics and bound with records




FOLIO snapshot stable will show these developments tomorrow. In relation to the bottom screenshot, Charlotte asked if the relationships should be explicitly labeled.

Suggestion: Adding a new element in the instance record called: Nature of content. Example of a labeled screen:


Could this be optional to display? Jacquie suggested having the option to define the relationship should be there. Natascha pointed out the redundant information that is present on this screen.

Natasha - How we are going to deal with analytics and bound withs at the item level is yet to be discussed by this group.


Update on mapping resource types, format, nature of content with Codex terms

"Resource" and "Format type" in Inventory did not correlate with the indexed. Felix brought up the aspect of describing what something is.

Felix: Terms from EBSCO Knowledge base are more granular. RDA 7.2.1.3 - local guideline - Example: Definition for "Journal" goes to an application profile. This maps to MARC, Nature of Content.

Natascha - Can we use an existing vocabulary?

Laura - This list is a good starting point.

Jacquie - Do we want to repeat this data or harvest from existing data?

Felix (in chat) - "if you have data like this, you should use the existing one :)"

Lisa (TAMU) - The advantage of this list is would make an easy place for programmers to access format information.

Jacquie - Will discovery layers get information from Inventory, or from

Felix Hemme has translated the core terms of rda 7.2.1.3 D-A-CH.: https://docs.google.com/document/d/15b5ZLN3ChRy8RKqTOpfmYLZ5sZtmJJ62RZ0u-B7ZWd4/edit

Sarah - purpose of Codex? Laura - The Codex is a federated search of data for resources held by the library.

Charlotte - There are constraints on the EBSCO terminology.

Jacquie - If Codex is used for technical services, what is the use case of this term in the Codex? If it's not being used for discovery, then what will this be used for. Charlotte - Codex is for internal use, yes. That may shift later. Jacquie - There is data harvested from the Codex already that could be used. Why add another vocabulary? Charlotte - there was a problem with thesis and dissertation that could not be expressed by anything in RDA. That started this discussion. Jacquie - This is a lot of vocabulary for that one use case. Sarah - Cornell's current catalog identifies thesis/dissertation by specific fields in the MARC record. Laura - This is the sort of data she was picturing would inform codex. She feels this would be useful beyond the Codex. If discovery is coming from inventory, then this would help. Jacquie - Even if this is only for the inventory, adding another thesaurus is not the way to go to surface ETDs. Most of these things are ____ from our current data. Laura - There

Group agreed to think more about this.

Everyone agreed there is an issue with inaccurate description of formats in discovery layers. What is the best way to solve this.

Lisa (TAMU) - is it possible to add it to test it? It would help us decide what we prefer.

Christie and Natasha (in chat)

Felix discussed talking to Julian from GBV.

Lynn - What are the ramifications of aligning to the EBSCO KB vocabulary, when other KBs will be coming into play?

VuFind installation: http://vufind-folio.scanbit.net/

Decision: Implement this element in the instance record, then we look when it is implemented, and consider if this is the right way to solve the problems. Initial problem - was mapping to the Code. Do we want to consider discovery along with the Codex at the same time?

Sarah -



From Felix Hemme to Everyone: 12:10 PM
@Charlotte: would you prefer that we use snapshot-stable for testing, if we are going to add issues in https://wiki.folio.org/pages/viewpage.action?pageId=7833356?
From Index Data to Everyone: 12:10 PM
Yes, that would be great Felix
From Felix Hemme to Everyone: 12:10 PM
ty!
From Index Data to Everyone: 12:11 PM
It’s snapshot stable the FOLIO tester also use
From Tiziana Possemato to Everyone: 12:13 PM
Again, I'm trying to follow you but great problem (I'm on the train) :-(
From Tiziana Possemato to Everyone: 12:17 PM
I'm trying to follow you but with a lot of difficulties due to internet connection on the train. Sorry a lot for this
From Ann Kardos to Everyone: 12:21 PM
Wonderful!
From Lisa TAMU to Everyone: 12:30 PM
this could be really good for filtering. I like this vocabulary, let's just use this! (teasing!)
From Felix Hemme to Everyone: 12:31 PM
if you have data like this, you should use the existing one :)
From Felix Hemme to Everyone: 12:36 PM
"schoolbook" this was the only term i was struggling with. could be a textbook, but the definition fits not exactly...
From Sara Colglazier to Everyone: 12:37 PM
@Felix what do you have for ebook?
From Felix Hemme to Everyone: 12:39 PM
2sec There is not term for ebook. I think this is because this terms are created to describe the "content" rather than "format".
From Sara Colglazier to Everyone: 12:39 PM
thanks
From Martina Schildt to Everyone: 12:40 PM
I agree to you, @Felix. And I think textbook would be the english term
From Lisa TAMU to Everyone: 12:45 PM
if I understand, although these names are already in different places in records, this would permit us to gather them into one place. Especially if we could have it automatically populate from teh other data elements. Good point!
From Christie & Natascha (UChicago) to Everyone: 12:47 PM
How is nature of content different from material type at the item level?
From Jacquie Samples to Everyone: 12:47 PM
We would also ask discovery layer developers to look at the new field and see what it looks like to the patrons.
From Mary Alexander to Everyone: 12:47 PM
I would need to investigate our collections and the proposed vocabulary. We have collections for children's literature, curriculum materials for K-12 grades for students and teachers and state approved text books K-12.
From Ann Kardos to Everyone: 12:47 PM
content can be different from material type
From Jacquie Samples to Everyone: 12:48 PM
Putting it in FOLIO, in other words, does not necessarily show us how the new field/data will show up in discovery.
From Felix Hemme to Everyone: 12:48 PM
@Ann good point, yes.


present?

Name

Organization

      Alice Krim
xAnn-Marie Breaux
xAnn KardosUMass Amherst

Charlotte Whitt
xChristie Thomas

Damian Biagi

Dennis Christman

Dracine Hodges

Felix Hemme

Filip Jakobsen
XJacquie SamplesDuke University

Jason Kovari

Jessica Janecki

Kimie Ou Yang

Laura Wright

Lisa Furubotten
xLisa McColl

Lisa Sjögren

Lynn Whittenberger
xMary AlexanderUniv. of Alabama


xNatascha Owens

Niels Erik Nielsen
xPatty Wanninger

Sarah Schmidt
xTiziana Possemato


xJenn Colt

Sarah Ross

Martina Schildt


xSara ColglazierMHC/5C