Page History

...

• RJ: This works only horizontally; / RT: Structure of representations is done by the Representation Metadata package
• JD: FRBR model: work->expression model / RT: departure from current system, may be confusing
• MS: attach attributes to the Files to explain to the system how to use them
• RJ: manifest file? / JD: this enforces the concept of an external metadata representation / MS: the system requires a metadata record / MS: lifecycle management issue requires that the data is there - doesn't file embedded metadata make the job harder / JD: yes, but that's concrete level
• RT: it's too difficult to put metadata in the relevant metadata buckets.
• JD: metadata needs to be a property at each level, not a separate entity at the top level (more FRBR) see diagram 2 below
• JD: make the model map to FRBR and let that squish; JMO: FRBR may not be appropriate in our use case at every level
• RJ: can we represent the "work" by collecting Items in metadata. MS: Item is an Expression, Representation a Manifestation, File = part of Manifestation

...