Also relates to resource management. Here’s some notes I sent to MM and RM SIG conveners last week:
Yesterday there was a FOLIO Day at Simmons in Boston, sponsored by the Fenway Libraries Online (http://www.flo.org/). It was a general intro to the FOLIO project, plus some emphasis on small/medium libraries and consortia. There were ca. 60 attendees. Main speakers were Neil Block, Mike Winkler, Sebastian Hammer, and Tania Fersenheim.
I facilitated a breakout on metadata & resource management, along with my colleague Marc Keepper. Here’s a few notes that I thought would be helpful to pass along for the RM and MM SIGs. Most important bits are highlighted.
Breakout 4: Metadata: Ann-Marie and Marc (ca. 15 librarians)
Is anyone taking part in any of the FOLIO SIGs? A couple folks had attended a couple sessions
Using other FOLIO communication channels? A little
Questions about anything you’ve heard this morning?
Some confusion that the codex meant that the source records would be taken apart (e.g. break apart the MARC record), making it hard to work with the data; explained that the source records would remain whole, but that the key data would be distilled into the codex for 1) indexing/searching across all metadata types and 2) to attach local data to, e.g. items, orders, holdings
What kinds of metadata are they managing?
MARC, MARC, and more MARC
Drupal for archives
Dublin Core; OAIdc? [whatever Content DM supports]
What are key topics they want to be sure FOLIO handles in terms of metadata?
Authority control – especially important for music; not handled well by discovery systems
Important to recognize and protect the unique stuff that has to stay that may not be in the master/source records
Should authority control be its own SIG? Maybe a subgroup within the MM SIG?
Do you use other open source software in your library?
Blacklight/Fedora for course reserves
Coral for ERM
Avalon for streaming audio and video
MarcEdit [not open source, but free]
For libraries that are not comfortable with a system that’s in such an early phase, they don’t want to have to start too early, when there’s not enough to play with and react to yet (we talked about people who get involved early (and have some input, like Purdue with Alma) and others who prefer not to, which is also fine
Why would everything have to get translated into MARC before showing up?
In FOLIO it wouldn’t (e.g. federated search against all various metadata types)
Lots of libraries do that (represent all in MARC), regardless of what may be in the IR or other metadata sources
Have a way to include types of data that may be important to a particular type of resource
— Be able to go to minute 2 of every oral history
— When an interview was done, location of interview
— Relationship between the interviewer and the subject (parent/child, teacher/student, spouse, etc.)
Being able to pull a shelflist (listing in call number order), to help with assigning call numbers, with accreditation stats
Some systems can’t easily do that
Some libraries want call numbers for E-content as well as physical, as another access/stats data point
Systems not forcing simplicity or conformity or complexity (e.g. complexity of circ policies, copy numbers, complexity of locations); not requiring lots of print overhead if the library doesn’t use print
Music and Visual Materials people not represented well in the SIGs yet, and they have special needs (the arts library communities)
Fenway Libraries Consortium: Voyager works; FOLIO feels scary and underdeveloped; leery about it being easy to get up and running, especially for a consortium
MARC is not implemented in the same way in every system, which can be extremely limiting
Single record approaches vs separate records in a shared catalog
Full-on holdings vs abbreviated holdings
Be able to have reporting out from FOLIO to the institution’s enterprise system (Banner or WorkDay or Other) so that they can run and make the payments
Having a workflow store, or a API store, or a report store; benefit from the work that other members of the community have already done
Some of the attendees are using Evergreen, so they’re already used to the idea of open source ILS
A benefit of open source: you have access to your data: can use system reporting tools, or develop own tools, or write a query
How you work with open source can change over time: maybe start with hosted system, then bring it in house
The idea of APIs are scary and intimidating (but they don’t have to be); individual FOLIO libraries won’t have to write their own APIs, but can if they want to