I just looked through the schema again and have noticed there is no contact defined for a collection. The institutional contact is the only one we have. This is probably because the institution was not "normalised" before but part of a collection record. So for every collection the institution could have provided a different contact. I suggest to add a collection contact to the schema (same structure as institution, preferrably vcard). -- Markus
On 05.06.2007, at 13:52, Markus Döring wrote:
+++++++++++++++++++++++++++++++++++++ I think we need to still take a decision on:
- multiple parent hierarchy. maybe we leave it single and discuss
it at the workshop?
- wording and meaning of "richRecordSearchString" vs
"collectionDatabaseURL". Can we agree to use "collectionObjectAccess" and "furtherDetails" both of which are URIs?
- CONTACTS. Wouldnt it be easier if we have a single contact class
(complextype) i.e. a vcard contact, that can be used for institution contacts as well as collection contacts? I would prefer this option to the strict selection of relevant contact fields for different purposes. The editor interface can still restrict this if we think thats needed. But NCD would be able to e3xchange an entire vcard record for a contact no matter where it is being used.
+++++++++++++++++++++++++++++++++++++