Hi Timo,
Further to Andrew's mention of the xMET tool that uploads and downloads
into any CSW system. The Office of Spatial Policy (OSP) located within
the Australian Government Department of Resources, Energy and Tourism,
have developed xMET with the help of the Australian National University.
We indend to make the Java application software available as Open Source
Software so that the community can contribute further enhancements to
xMET.
OSP also manages the http://www.mymaps.gov.au/ web site which we hope
will be a replacement for the ANZLIC Australian Spatial Data Directory
(ASDD) located at http://asdd.ga.gov.au/asdd/. The ASDD is a remote
search catalogue system which provides a web interface to search more
than 20 metadata repositories located around Australia.
The http://www.mymaps.gov.au/ web site is based on GeoNetwork and
harvests metadata records from about 23 different Z3950 servers. Many of
these are the same repositories and mentioned above. The process of
managing the information about these repositories is as follows:
1. a person 'registers' themselves as a 'harvesting node'. This is not
an option in the 'profile' list but I hope that someone will add it. I
guess I need to add a request of some sort?
2. The user is accepted by the mymaps manager and allocated a node
identifier and a node manager's group eg. 'aims-node'.
3. They user then fills out a service metadata record of the node they
wish to have harvested and stores it on the GN catalogue.
4. The mymaps manager then uses the service metadata content to harvest
metadata from that havesting node. A 'Category' is added for the
harveted node, the URL of the service is used for setting the harvesting
process eg. Z3950://asdd.ga.gov.au:6668/ga/ and how often the harvest is
to be done. Usually every day. The service itself is checked every hour
on the half hour so that if the node is down for let's say four
consecutive hours, then the node manager (email address in the
'register' information) is notified that there is a problem and then
they can fix the problem.
5. If the harvesting node details change then the node manager makes the
changes via the service metadata record.
6. Every hour on the half hour GN checks the service metadata records in
the harvesting group and then notifies the mymaps manager of any changes
needed for harvesting. This should then be adjusted in the harvesting
details but I think that this has to be done manually. Hence and email
needs to go to the mymaps.gov.au manager to tell them to edit the
harvesting details.
7. The mymaps manager makes the changes to the harvesting interface.
8. The mymaps GN harvests the metadata from the nodes according to the
settings made by the mymaps manager.
Simon Pigot has written much of the software that processes most of
these functions but there are a few things still missing. Simon and I
have discussed this work flow in detail and I hope to get some changes
to GN once I have the time. ;--)
There are different types of nodes. They are:
1. Where the metadata is provided by a service external to the mymaps GN
system.
2. Where the metadata is held on the mymaps GN system and the users use
xMET or ANZMET Lite to download and upload the metadata to the mymaps GN
CSW.
3. Where the entire GN system is backed up from another web site. We
have verbal agreement with LINZ in New Zealand to backup each others GN
system but I still haven't had enough time to properly set and test that
process.
I hope that this helps.
John Hockaday.
-----Original Message-----
From: andrew walsh [mailto:awalsh@anonymised.com]
Sent: Wednesday, September 14, 2011 10:25 AM
To: Timo Proescholdt
Cc: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] inquiry / usage of GN for MD
maintenanceoutthere
Hello Timo,
Here at RAN Metoc services we have maintained a Geonetwork with
ISO19139 for some time now so I thought I would share our experiences.
You are right the ISO19139 editor is very detailed and
technical. To make it
easier for non-technical users we use templates. Typically
users only need to
enter of change a few items on the template i.e. Title,
Abstract, bounding box,
keywords, creation date, 'edition details' and 'environment
description'.
However
in saying that the users need to to follow the 'instruction
sheet' to the letter
and not
accidently stray into the many other fields on the template.
So this is not a
error free
process.
For some other metadata creation we have an automatic process
using parameters
passed to an XSL script e.g construct an abstract, title and
bounding box. This
automatic
creation is a lot easier and less error prone.
We have not hit the issue of different departments entering
metadata as we are
just one
here. I know that Geonetwork now has a 'logo management'
feature which could in theory be used to designate different
branches in an
organisation.
Metadata are tagged by different logo's and source-uuid and
using the Advanced
Search->RestrictTo->
Catalog drop down its possible to search by logo/source.
Perhaps some other
organisations with many departments could share their
experiences on how they
manage this.
There are 2 software projects I know of that are designed to
make the process of
metadata
entry much simpler. These software are editors that make
standalone XML
documents which can
later be imported into a corporate Geonetwork server.
Firstly there is the 'ANZMet Lite' editor (see
http://www.osdm.gov.au/Metadata/ANZLIC+metadata+resources/ANZM
et+Toolkit+%28final+draft+-+07.2009%29/default.aspx)
which uses a wizard based tabbed workflow.
ANZMetLite was designed with the ISO19139-ANZLIC profile in mind.
Secondly there is the newer xMet editor under development
(see blog at
http://www.mymaps.gov.au/blogs/xmet/ ) which allows an
administrator to
construct customised data entry forms. The xMET data entry
form can focus on
exactly the data items needed to be entered making it very simple and
non-technical. xMET
allows plugging in of different metadata standards and
profiles of those. We
have
done some testing with xMet Lite using the ISO19139-MCP profile.
Andrew
----- Original Message -----
From: "Timo Proescholdt" <timo@anonymised.com>
To: <geonetwork-users@lists.sourceforge.net>
Sent: Tuesday, September 13, 2011 6:10 PM
Subject: [GeoNetwork-users] inquiry / usage of GN for MD
maintenance outthere
> Dear GN-users,
>
> I would like to learn more about how GN is used out there,
especially in
> an organizational environment where ISO19139 metadata needs
to be created
> and maintained.
>
> It seems to me that, for all its qualities, the ISO19139
editor is still
> pretty complicated. So one question is how users charged
with maintaining
> the metadata, who are often non-technical, deal with this?
>
> I would also be very grateful if someone could share some
experiences on
> the sort of organizational structure around metadata management, for
> example if different departments are supposed to maintain
metadata. How do
> you represent this in GN?
>
> When it comes to managing metadata, it seems to me that an
organizational
> structure and processes are needed. This has nothing to do with the
> software itself, but maybe someone can share some insights.
>
> thanks very much and
> best regards
> Timo
>
>
>
--------------------------------------------------------------
----------------
> BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
> Learn about the latest advances in developing for the
> BlackBerry® mobile platform with sessions, labs & more.
> See new tools and technologies. Register for
BlackBerry® DevCon today!
> http://p.sf.net/sfu/rim-devcon-copy1
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>
>
--------------------------------------------------------------
----------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a
new level of
agility. Learn what those decisions are and how to modernize
your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
*************************************************************************
The information contained in this e-mail, and any attachments to it,
is intended for the use of the addressee and is confidential. If you
are not the intended recipient you must not use, disclose, read,
forward, copy or retain any of the information. If you received this
e-mail in error, please delete it and notify the sender by return
e-mail or telephone.
The Commonwealth does not warrant that any attachments are free
from viruses or any other defects. You assume all liability for any
loss, damage or other consequences which may arise from opening
or using the attachments.
The security of emails transmitted in an unencrypted environment
cannot be guaranteed. By forwarding or replying to this email, you
acknowledge and accept these risks.
*************************************************************************