Changes between Version 4 and Version 5 of registers

Timestamp:

Oct 25, 2011, 8:06:04 PM (13 years ago)

Author:

simonp

Comment:

--

registers

@@ -35 +35 @@
  * Vocabularies, codelists and thesauri are held in static files external to the !GeoNetwork catalog. The process by which items in these registers are modified, updated, superseded or retired are invisible as the formats they are held in do not support capture of this information. 
  * Metadata records that use items from these registers usually do so by referencing an external document (eg. http://asdd.ga.gov.au/asdd/profileinfo/anzlic-theme.xml)
- * Often the codelist has been converted to yet another format eg. for use in the !GeoNetwork editor the ISO19139 codelists in http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml are converted to a codelists.xml file and stored in the localized GeoNetwork directory. Recording and propagating changes to a codelist in this environment is difficult to say the least. 
+ * Often content of a register has been copied to another format eg. the ISO19139 codelists in http://www.isotc211.org/2005/resources/Codelist/gmxCodelists.xml is copied into a codelists.xml file and stored in the localized !GeoNetwork directory for use by the !GeoNetwork editor. This should be modified so that the register content is not copied, only the association between the register and an element is held otherwise recording and propagating changes to register content is too difficult. 
 
-The motivation for this proposal is to capture register changes in the register, make registers transportable between catalogs through harvesting, and converge access to one register format.  
+The motivation for this proposal is to capture register changes in the register, make registers transportable between catalogs through harvesting, and hold the register content in ISO19135 which is then accessed by everything (hmm).  
 
 == Proposal == 
@@ -44 +44 @@
  * Develop an XSLT to convert the ISO19139 CT_CodelistCatalog format to ISO19135 register format
  * Add ISO19135 register records to ISO metadata schemas and profiles (to be loaded with the schema/profile or regularly harvested into !GeoNetwork category 'Registers')
- * GeoNetwork looks up the codelist item in the list of register records associated with the metadata schema of the metadata record being edited 
+ * Remove register content from codelists.xml file. Instead this file will hold associations between elements and registers. Example for iso19139.anzlic :
+   {{{
+       <registerAssociation registerId="uuid_of_GA_register" element="gmd:MD_ScopeCode"/>
+       ....
+       .... 
+   }}}
+ * !GeoNetwork looks up the codelist item in the list of register records associated with the metadata schema of the metadata record being edited. 
  
 === Backwards Compatibility Issues ===