[GeoNetwork-devel] ISO 19139, profiles and and othe questions about the interaction with GeoNetwork

GeoNetwork GeoNetwork Developer
1

Hi all,

As you may be aware my colleague Michael Gannon is investigating setting up
GeoNetwork as a prototype to manage our organisation's ISO 19115 metadata.
We will probably use GeoNetwork as a prototype to enter, edit and store
metadata as well as get users to identify their requirements of a CSW.

As you know a while ago I mentioned about the ISO 19139 XSDs on this list and
thanks to Jeroen, Andrea and probably others, GeoNetwork now somehow handles
the ISO 19139 XML metadata format. I think that I also mentioned that the
ISO 19139 XML implementation doesn't cater for all the ISO 19115 constraints
and code lists so ANZLIC - the Spatial Information Council (for Australia and
New Zealand) is cloning the ISO 19139 XSDs, adding Schematron to these cloned
XSDs and creating XML to represent the different ISO 19115 and ANZLIC code
lists. We are also adding XSDs and Schematron that allows for ISO 19119
metadata. That is, metadata for "services". The XSDs were taken from the
eden web site mentioned in my previous emails but the Schematron, again
handles the constraints that the XSDs can't implement.

Michael is using GeoNetwork 2.1.0 alpha-1 and has posted a couple of problems
that he has encountered to this list. I also have the following questions
which I hope you can answer to help us decide if we will use GeoNetwork for
our prototype. The question s are:

1. Is it easy to configure GeoNetwork to use our ANZLIC metadata profile
XSDs?

2. Can GeoNetwork 2.1.0 alpha-1 bulk import GeoNetwork XML document
instances?

3. Can GeoNetwork 2.1.0 alpha-1 bulk import ISO 19139 XML document instances?

4. If not has someone developed and XSL that translates ISO 19139 XML
document instances into the XML format that GeoNetwork uses?

5. If not does someone *intend* on creating an XSL that translates ISO 19139
XML document instances into the XML format that GeoNetwork uses?

6. If we do import ISO 19139 XML document instances, can we edit, update and
delete them?

7. Can GeoNetwork 2.1.0 alpha-1 bulk export ISO 19139 XML document instances?

8. If not can GeoNetwork 2.1.0 alpha-1 bulk import bulk export GeoNetwork XML
document instances?

9. If so has someone developed an XSL that translates from GeoNetwork XML
document instances to ISO 19139 XML document instances?

10. If not does someone *intend* on developing an XSL that translates from
GeoNetwork XML document instances to ISO 19139 XML document instances?

11. Is it easy to configure GeoNetwork 2.1.0 alpha-1 advanced search
interface to search for other ISO 19115 elements such as, multiple
hierarchyLevelNames? For example, search for all metadata about "software"
or all metadata about "dataset" and "series".

12. Can GeoNetwork access web accessible folders for the bulk harvest of XML
metadata records or must it have a compliant Z3950 server to access those XML
documents?

If the answer to any of these questions is "yes" can we please have the XSLs
or the location of the documentation that tells us how to configure
GeoNetwork 2.1.0 alpha-1 to do this.

I thank you in advance for any answers to these questions that will help us
decide if we use GeoNetwork for out prototype CSW.

Thanks.

John

2

Hi John,

I will try to answer to your questions.

-1-----------------

In general, adding a new schema consists of 3 steps in increasing order of complexity:
- add another folder in web/xml/schemas with the proper XSD files (pretty easy)
- add a lucene stylesheet to index the queryable fields (easy).
- add visualization stylesheets (medium complexity, depends on how big the schema is)
- add editing stylesheets (hard)

In your case you have also to find a way to use schematron because geonetwork does not
support it.

-2-----------------
Yes, you can use the batch import functionality.

-3----------------
Yes, but I don't see the difference respect to the previous question. Geonetwork
supports the ISO19139 so you can import it. If you mean the ANZLIC 19139,
once you added the schema (answer 1) you can use batch import.

-4------------
I don't understand the question. Geonetwork stores metadata in XML string format
so for me it does not make sense to convert an ISO19139 metadata into a
geonetwork's one.

-6---------------
yes. We are improving the editor to make it working with the ISO19139.

-7 and 8---------------
now there is no functionality to export metadata. There is an XML service to
export one metadata at time given its id. To cover this aspect, we will soon
start to add inport/export capabilities in order backup data and metadata or
move it to another (even newer) geonetwork instance. (planned by December).

-9---------------
same as 4

-11-----------
yes it is. You have to change the indexing stylesheet (a short one) and to add
those fields to the web form (another simple stylesheet).

-12------------
I'm currently working on a 'web folder' enabled harvesting but I don't know if this
answer to your question.

Cheers,
Andrea

Hi all,

As you may be aware my colleague Michael Gannon is investigating setting up
GeoNetwork as a prototype to manage our organisation's ISO 19115 metadata.
We will probably use GeoNetwork as a prototype to enter, edit and store
metadata as well as get users to identify their requirements of a CSW.

As you know a while ago I mentioned about the ISO 19139 XSDs on this list and
thanks to Jeroen, Andrea and probably others, GeoNetwork now somehow handles
the ISO 19139 XML metadata format. I think that I also mentioned that the
ISO 19139 XML implementation doesn't cater for all the ISO 19115 constraints
and code lists so ANZLIC - the Spatial Information Council (for Australia and
New Zealand) is cloning the ISO 19139 XSDs, adding Schematron to these cloned
XSDs and creating XML to represent the different ISO 19115 and ANZLIC code
lists. We are also adding XSDs and Schematron that allows for ISO 19119
metadata. That is, metadata for "services". The XSDs were taken from the
eden web site mentioned in my previous emails but the Schematron, again
handles the constraints that the XSDs can't implement.

Michael is using GeoNetwork 2.1.0 alpha-1 and has posted a couple of problems
that he has encountered to this list. I also have the following questions
which I hope you can answer to help us decide if we will use GeoNetwork for
our prototype. The question s are:

1. Is it easy to configure GeoNetwork to use our ANZLIC metadata profile
XSDs?

2. Can GeoNetwork 2.1.0 alpha-1 bulk import GeoNetwork XML document
instances?

3. Can GeoNetwork 2.1.0 alpha-1 bulk import ISO 19139 XML document instances?

4. If not has someone developed and XSL that translates ISO 19139 XML
document instances into the XML format that GeoNetwork uses?

5. If not does someone *intend* on creating an XSL that translates ISO 19139
XML document instances into the XML format that GeoNetwork uses?

6. If we do import ISO 19139 XML document instances, can we edit, update and
delete them?

7. Can GeoNetwork 2.1.0 alpha-1 bulk export ISO 19139 XML document instances?

8. If not can GeoNetwork 2.1.0 alpha-1 bulk import bulk export GeoNetwork XML
document instances?

9. If so has someone developed an XSL that translates from GeoNetwork XML
document instances to ISO 19139 XML document instances?

10. If not does someone *intend* on developing an XSL that translates from
GeoNetwork XML document instances to ISO 19139 XML document instances?

11. Is it easy to configure GeoNetwork 2.1.0 alpha-1 advanced search
interface to search for other ISO 19115 elements such as, multiple
hierarchyLevelNames? For example, search for all metadata about "software"
or all metadata about "dataset" and "series".

12. Can GeoNetwork access web accessible folders for the bulk harvest of XML
metadata records or must it have a compliant Z3950 server to access those XML
documents?

If the answer to any of these questions is "yes" can we please have the XSLs
or the location of the documentation that tells us how to configure
GeoNetwork 2.1.0 alpha-1 to do this.

I thank you in advance for any answers to these questions that will help us
decide if we use GeoNetwork for out prototype CSW.

Thanks.

John