J. Wolfgang Kaltz wrote:
Hi list,
a few weeks ago we discussed changing the metadata handling, to
1. make metadata for a document mandatory;
2. store the metadata separately from the contents
3. add some Lenya-specific, non dublincore metadata, specifically the
Lenya resource type within the metadata
1. & 2. basically just mean handling document metadata identically to
the way meta-data is currently handled for assets; this does not seem to
require many changes. However I'd like your input whether I've
overlooked something before checking anything in:
Changes are
- DefaultDocument.java: work similar to Resource.java, that is: get
metadata from a different URI than the contents. Add this source in
getRepositoryNodes for locking
That sounds very good. Maybe it makes sense to generalize DefaultDocument
and Resource re. the external meta data handling, or delegate this code
to another class.
-- Andreas
- remove meta stuff from the samples
- remove meta stuff from the schemas
Do you see any other things to consider ? I've tested editing in
oneform, and the meta usecase for editing metadata. Testing in BXE and
Kupu is incomplete, since the editor integration is not finished in
trunk, but I suppose those editors don't care about Lenya metadata.
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
