Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated linkt to slides


Additional notetaker?

Lisa needs to leave at the hour. If we run later, can someone volunteer to pick up the notetaking?

Charlotte & Laura will

Product Council UpdateA discussion about implementation guidelines continued. Some schools will begin with a partial implementation. Some full implementations are still planned for 2020. As far as Dracine knows, Chalmers is still planning on implementing in 2019.
Subgroup Updates
CodexVince Bareau

Vince Bareau will join us to talk about the Codex. Vince Bareau - Could we please get your updated version of this?

Plan on a slightly longer meeting (12-1:30 EST).




  • The domain in the context of FOLIO contains modules that share properties and characteristics. There is a shared vocabulary within a domain. Within the Codex domain is mod-codex-mux , mod-codex-ekb, mod-codex-inventory
  • Linked data support by Codex: The notion of Codex provides a bring that links various domains together.
  • The Codex will be a place to hold defined relationships.
  • MarcCat will communicate with mod-inventory.
  • How does Codex relate?
    • Charlotte: Will there be arrows in the Working Records layer? Vince - We should minimize those. There may be occasional needs, but as a rule, they should not interact.
    • This slide is intended to give perspective that all of the domains are not the same. The domains do not operate at the same level.
  • Use Cases

Questions arose about what the search results in the Codex would look like. Chicago made the point that bibliographic information is so closely related to acquisitions information. Vince pointed out that identifiers between


Question (Five Colleges): When you order a resource, one use case is to export a bib record from OCLC. If acquisitions is separate from the inventory domain, how would this work? And how would that bib record linked to the order record be stored?

Answer: Take exported MARC record from OCLC, create an order that would link back to the source record. That info would not go into Inventory until the item is actually held.

Question (Sara): What in Codex will show that a second copy is on order?

Answer: Items on order are handled by acquisitions. When no longer on order, a receiving process will bring that into Inventory. The responsibility shifts to Inventory. Inventory will report then to Codex. Codex results set will show both : owned from Inventory and on order by Acquisitions.

Question (Ann-Marie): An e-resource could be held in Inventory and KB, how does Codex show that?

Answer: It will show one line fed by Inventory another line fed KB to the Codex.

Discovery will sit on top of Codex.

Jason - Why would we want this paired down data to be the information in discovery layer?
Vince - Codex will contain links to the more detailed versions of the records that can be called upon as needed.

Felix – are there performance/reliability concerns around sending every request through Codex?

Charlotte – suggestion for Linked Data working group that includes MM, Codex, RM

At what stage does something move from Acquisitions to Inventory? Can this be flexible/customizable? – ideally, yes

Use cases for ongoing orders, e.g. a serial or standing order? this is configuration, not dependent on Codex

Codex could be the place where all authorities are managed.

Jacquie: how would Codex link to external authorities/identifiers?

Codex as way of sharing info cross-tenant

Is it a single Codex or multiple Codexes (across libraries)? – one Codex within each FOLIO system

What type of data storage is being envisioned in Codex?



This would be a huge change. Will need to go through Technical Council.