In ISO19139 some people would like to set the fileIdentifier of a metadata
record themselves. This can be achieved by creating a profile of iso19139
that allows editing the field.
However, the fileidentifier is closely linked with the uuid column in the
database and via this also to, inter alia, the identifier in a OAI-PMH
list response.
I want the OAI-PMH identifier to be the same as the ISO fileidentifier.
One way to implement this would be to link the OAI-PMH identifier to the
ISO filedentifier, but this does not work for all metadata types and also
has issues with guaranteeing uniqueness of a filenameidentifier.
So one could think about generating the uuid from the fileidentifier, in
some cases. However, looking at the code I see that the UUID is generated
when a record is first created, even before it is stored in the system. I
wonder why this is and if this can be changed?
It seems that for interaction with the server, GN uses the value of the id
column, which is independent of the uuid, so I do not see why the uuid
needs to be generated before the record is stored first. One could delay
generating a uuid until the record is stored for the first time, and then
take the ISO fileidentifier value if it is there, under the understanding
that it is unique.
Does this sound feasible?
Timo
Hi,
I thin your is a good question.
I has many metadatas (some thousands, all with parent/childs relations)
All of they surely have an unique FileIdentifier, but unfortunately it is not an UUID standard value.
I was able to load in GN using the batch-import, with the option load “no action on import”
to avoid the unwanted change of all their FileIdentifier Value.
This unfortunately cause some problem when try to browse the metadata because they are all parent/child and the GN system want an UUID in the FileIdentifier to allow the link between parent and childs.
So for me is surely prefereble to leave the original Fileidentifier and usa an internel UUID retrieved from the FileIdentifier value.
Andrea.
2011/6/7 Timo Proescholdt <timo@anonymised.com>
In ISO19139 some people would like to set the fileIdentifier of a metadata
record themselves. This can be achieved by creating a profile of iso19139
that allows editing the field.
However, the fileidentifier is closely linked with the uuid column in the
database and via this also to, inter alia, the identifier in a OAI-PMH
list response.
I want the OAI-PMH identifier to be the same as the ISO fileidentifier.
One way to implement this would be to link the OAI-PMH identifier to the
ISO filedentifier, but this does not work for all metadata types and also
has issues with guaranteeing uniqueness of a filenameidentifier.
So one could think about generating the uuid from the fileidentifier, in
some cases. However, looking at the code I see that the UUID is generated
when a record is first created, even before it is stored in the system. I
wonder why this is and if this can be changed?
It seems that for interaction with the server, GN uses the value of the id
column, which is independent of the uuid, so I do not see why the uuid
needs to be generated before the record is stored first. One could delay
generating a uuid until the record is stored for the first time, and then
take the ISO fileidentifier value if it is there, under the understanding
that it is unique.
Does this sound feasible?
Timo
EditLive Enterprise is the world’s most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
–
Andrea Peri
. . . . . . . . .
qwerty àèìòù