Search

Help

Page 2 of 24. Showing 239 results (0.014 seconds)

  1. Re: The Codex Vision - TC Review

    as the Codex data model. The Inventory Instance is already a normalization. I am leery of the idea of normalizing normalized data. The Instance normalization meets needs identified in numerous use cases. While I'm not particularly concerned with *where* authority data live (e.g., in Inventory, in Codex, or in some other
  2. graph-color.pdf

    -storage-5.1.0 mod-gobi-1.0.1 mod-event-config-1.0.0mod-erm-usage-harvester-1.0.0 mod-erm-usage-1.0.0 mod-data-import-1.0.0 mod-codex-mux-2.3.0 mod-codex-mock-2.1.0mod-codex-inventory-1.4.0 mod-codex-ekb-1.1.0 mod-circulation-storage-6.2.0mod-calendar-1.2.0 mod-audit-filter-0.0.3 mod-audit-0.0.3mod-agreements
  3. Re: The Codex Vision - TC Review

    I was leaning towards the Codex and then after today's metadata management meeting am leaning towards inventory with no codex. However, I'm still asking questions about use cases and Folio working from the ground up. One place where Inventory and Codex might not be identical is discovery. And some of my thoughts
  4. Re: The Codex Vision - TC Review

    > I'd also like to point out that the Inventory data model as it stands now is identical to what was originally proposed as the Codex data model The Inventory data model is not identical to what was proposed for Codex. It was based-on the Codex model but then many more fields and structures were added - as would
  5. Re: The Codex Vision - TC Review

    "Codex is a normalization and virtualization layer that allows Folio to integrate metadata about various resources regardless of format, encoding, or storage location." Point of clarification: the Codex is only virtual if it is recreated on the fly at each use, i.e., the Codex doesn't exist in any semi-permanent
  6. Re: The Codex Vision - TC Review

    if communication with a future app can't be predicted? Would it be easier to just write one communication standard which is the codex? In many ways, I'd like to hear what the developers and sys op people think about this. Could it be that the codex turns more into a back end search and communication mechanism and we as users work
  7. Re: The Codex Vision - TC Review

    If I'm understanding correctly, in this role Codex would be working behind the scenes, relaying information? So that, for instance, Inventory and Orders would both share information with Codex, and Codex might share information gathered from Orders with Inventory – rather than Inventory and Orders sharing information
  8. graph-color.pdf

    -storage-5.1.0 mod-gobi-1.0.1 mod-event-config-1.0.0mod-erm-usage-harvester-1.0.0 mod-erm-usage-1.0.0 mod-data-import-1.0.0 mod-codex-mux-2.3.0 mod-codex-mock-2.1.0mod-codex-inventory-1.4.0 mod-codex-ekb-1.1.0 mod-circulation-storage-6.2.0mod-calendar-1.2.0 mod-audit-filter-0.0.3 mod-audit-0.0.3mod-agreements
  9. Re: The Codex Vision - TC Review

    that an electronic KB is useless? There are already more than 2 resource data models in Folio: MARCcat inventory; KB; orders; codex. Each has their own specialized … (what I'm calling domains here). The very notion of Codex is to avoid the problem of the every growing universal data model. A data model that would become
  10. Re: The Codex Vision - TC Review

    to present fairly limited bibliographic metadata (but exquisitely precisely honed holdings information).  The very notion of Codex is to avoid the problem … number of elements irrelevant to any one of the domains. This is the justification that I have presented in the past where Codex seeks the intersection