Dear all,
over here we are now doing some tests with GeoNetwork 2.10.1. We have
serious problems with editing metadata.
The problem is, that I do not find any possiblitiy to make GeoNetwork create
a uuid for the MD_Metadata / fileIdentifier in the xml of the metadata.
Either it is always the same uuid for MD_Metadata / fileIdentifier or it is
missing and looks like this in the xml-metadata:
<gmd:MD_Metadata xsi:schemaLocation="http://www.isotc211.org/2005/gmd
http://www.isotc211.org/2005/gmd/gmd.xsd http://www.isotc211.org/2005/srv
http://schemas.opengis.net/iso/19139/20060504/srv/srv.xsd">
<gmd:fileIdentifier>
<gco:CharacterString/>
</gmd:fileIdentifier>
...
----------------------------------------------
For testing I used a templed we created some time ago with GeoNetwork 2.4.x
/ 2.6.x / and I used the template "iso19139... preferred" coming with
GeoNetwork 2.10.1. For editing the metadate I took the following steps:
1. I created a new group catalogue "testdatensaetze".
2. I created an editor, a reviewer and a user admin for "testdatensaetze".
3. The editor created the dataset metadata, but even after saving the GUI
shows for the MD_Metadata / fileIdentifier "Value will be set when record is
saved."
4. The reviewer set the prviledges, but it is all the same >> after
modifying the metadata the GUI shows for the fileIdentifier still "Value
will be set when record is saved."
After that I logged off / on with several users. The right-management works
perfectly fine.
*Here is the result for the GeoNetwork-Template I "iso19139... preferred":*
The uuid for the fileIdentifier won´t show up. It´s not even in the xml of
the metadata created from that template. In fact, this template has not a
MD_Metadaten / fileIdentifier. That might be okay. Templates do not need no
MD_Metadata / fileIdentifier. Metadata need MD_Metadata / fileIdentifier.
With the MD_Metadata / fileIdentifier you create the GetRecordById Request
for CSW. So I tried that one just the way I always did in GN 2.6.4:
Click on the "Permanent link for the metadata", so that the fileIdentifier
uuid shows up in the url-field of the browser. But: As soon as I click on
"show metadata" in the search-results, there is an error message:
"Die angefragte Aufgabe konnte nicht erledigt werden.
XPathException : Template UNKNOWNBrief has not been defined"
Okay, not so much of a problem for us we use a template of our own (I
thought. But the truth is, the problem might come from the missing
MD_Metadata / fileIdentifier.)
-------
*Here is the result for the template of our own, originally coming from
2.4.x / 2.6.x:*
I created three dataset metadata with the template of our own. We always use
that template and it has 74088940-18c1-404e-a65c-650aa7b53461 as an
MD_Metadata / fileIdentifier after importing in GeoNetwork 2.10.1. This uuid
from our template off course has not been used over and over again by the
older GeoNetwork versions, because for each new metadata created from that
template, GeoNetwork creates a new uuid as MD_Identifier / fileIdentifier
for each metadata.
Unfortunately in GeoNetwork 2.10 and in GeoNetwork 2.10.1 GeoNetwork just
keeps the static uuid for each metadata. But, when you use the button
"permanent link to metadata" you can see the true uuid in the browser
because the url is displayed here. For the url-field of the browser all
metadata have an unique uuid. Problem: this uuid does not show up in the
xml-metadata. A GetRecordById Request cannot be answered (There is a
response, saying <csw:GetRecordByIdResponse/>; so it is all empty.)
This is a serious problem, I think. Please don´t refer to the workaround
taken the uuid from the browser and putting it into the xml-metadata via
xml-editing of the GUI. It might work, although I haven´t checked, but
people editing metadata hardly know what an url, a browser or an uuid is.
Any help highly appreciated. I am so sorry, if this was a true bug Do we
have any chance in trying another configuration of anything?
Greetings,
Anja
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/GeoNetwork-2-10-2-10-1-MD-Metadata-fileIdentifier-either-not-unique-or-missing-in-xml-metadata-tp5072731.html
Sent from the GeoNetwork users mailing list archive at Nabble.com.