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
- 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
begin:vcard fn:J. Wolfgang Kaltz n:Kaltz;J. Wolfgang email;internet:[EMAIL PROTECTED] tel;work:+49 203 379 2276 tel;fax:+49 203 379 3557 x-mozilla-html:FALSE version:2.1 end:vcard
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
