Hi,
I have placed a test version of the AIMS customised BlueNetMEST for you
to have a play with. It has the parent child relationship implementation
I came up with for AIMS (no search functionality). You will need to work
with the iso19139.mcp schema to see this as it's the only schema I have
implemented it on. Also only English language is supported.
http://data.aims.gov.au:9080/geonetwork
Login is default admin account.
Where do we stand with the proposal for this parent child relationship
implementation, did you still want me involved?
Cheers,
Kevin
-----Original Message-----
From: Kevin Gunn
Sent: Monday, 17 November 2008 10:44 AM
To: 'francois-xavier.prunayre@anonymised.com'
Cc: geonetwork-devel
Subject: RE: [GeoNetwork-devel] parent and child relationships
Hi Francois,
With regard to record ownership, I leave it set up the defaults, that is
I let any editor create children, I don't restrict this at the moment
(default create button privileges). Once created, then if the creator
isn't the one who should own the record they would need to transfer
ownership to the appropriate editor and group. I have introduced single
ownership transfer to our internal Geonetwork. I see this is now part of
the latest "massive" operations functionality. I implemented the single
transfer slightly different, via a new button on the record show form
that only displays according to the same privileges as the edit button.
With regard to catalogues, I haven't included this concept in the parent
child relationship. Currently I'm only designing/implementing for
linking records in the local Geonetwork. The parents could be harvested
records, but I wasn't going to link to a remote Geonetwork. I haven't
factored harvested records into the equation yet so will have to do some
testing on that. Do you need to have the linkage directly to remote
nodes?
I'd like to post my source somewhere externally so you can compile it
and have a look, check out the source code, etc. How do I go about
getting an area on the SVN for this?
Cheers,
Kevin
-----Original Message-----
From: Francois-Xavier Prunayre
[mailto:francois-xavier.prunayre@anonymised.com]
Sent: Thursday, 13 November 2008 17:48 PM
To: Kevin Gunn
Cc: geonetwork-devel
Subject: RE: [GeoNetwork-devel] parent and child relationships
Hi Kevin,
On jeu, 2008-11-13 at 11:25 +1000, Kevin Gunn wrote:
Checked out your geonetwork url and tried the "land cover" search but
it
returned no records for me. Nor did "la couverture des terres" :-). I
had not authenticated though.
Yep, some people are playing with this website, so content is changing.
But feel free to login (admin/admin) and you could try creating a child
from an existing record.
-automation of child->parent and parent->child linkage creation in
create
-automation of parent->child linkage removal in delete
This work only when all your metadata records are in the same catalogue
but you could have a child referencing a parent in another catalogue ...
uuidref are unique but could point to a ressource in a different
catalogue.
Do you have issue on metadata own by one user and the child own by
another editor ... then you could have cases where user doesn't have
privileges to do an update of both parent and children ? How do you
handle that ?
-automation of child->parent and parent->child linkage creation and
removal in update
-allowing creation of child and sibling relationships via the
create/duplicate service and setting up the appropriate child->parent
and parent->child linkage
-failing delete on parents that have children
-href link in show form only when string length of parentIdentifier
and
childIdentifier fields is 36 (UUID length)
this. Guess I could have some sort of recursive lucene search.
For now in geosource, it's only a two steps search ... but definetely it
could be useful to do recursive search. It could be nice to do the main
search and then in the present service search for related items so we
could display search results with :
* record 1
* parent
* children
* services (19119)
* featureCatalogue (19110)
* record 2
* services
* record 3
* record 4
* ...
Ciao.
Francois
--
------------------------------------------------------------------------
The information contained in this communication is for the use of the
individual or entity to whom it is addressed, and may contain
information which is the subject of legal privilege and/or copyright.
If you have received this communication in error, please notify the
sender by return email and delete the transmission, together with any
attachments, from your system. Thank you.
------------------------------------------------------------------------