Dear all:
Not sure whether this is the place for the community to contribute to "specification development"....
however, here's my 2 cents worth on comments on the GN-developers list yesterday (Andrew's "harvest" flag comment; others logo upload GUI comments), and whether logos are an indicator of ownership, etc....
I agree that it would be great if a harvested record displayed a "harvested" flag, in GeoNetwork, but I think we need to spec out the broader need, as well.
Ideally GeoNetwork would provide for harvested records to carry, and be able to display to the user, "harvest history" information, such as
i) the source of the harvest-event,
ii) date of harvest
iii) some text signifying the "owning institution" of the metadata
record (as specified by the metadata creator),
iv) the owning catalog of the record
(again - this would be "set" by the metadata creator), and
vi) the logo(s) that should displayed with a record.
vii) the metadata standard /profile of the original record, and
viii)the filesize (?or number of fields?
Something that can be used to quickly see whether a record
has been subsetted)
And this history would build, where a record was harvested from one catalog to another to another.
GeoNetwork would ideally have default creation of the above, but with the originator/owner of the record having the option to stipulate what is to be in iii) to v), for where the record is harvested.
Within a harvesting GeoNetwork, it would be great if you could limit or customise whats seen, such as only showing the "harvested" flag, and [possibly] text describing the "owning Catalog"; and only show the logo(s), etc, after the clicking "Harvest information".
One issue is: harvesting is already commonly performed iteratively (recordX, created in Catalog A is harvested into Catalog B. Catalog C harvests all records in Catalog B, and then Catalog D harvests Catalog C. At present, Catalog D would display recordX, but the logo initially added by Catalog A isnt shown)
A question that needs to be resolved is: what is the logo meant to be for. Is it to signal :
a) the "owning"/original catalog (which might not be publicly accessible),
b) the source "public" catalogue that the record was first harvested from, or
c) the latest catalogue that the record was last harvested from.
Ideally a harvested record would carry its harvesting provenance.
===========================================
Some scenarios below (which I'm sure are also true for many others) illustrate some of the issues:
IMOS is a project that has funded partners who all have their own Geonetwork instance.
IMOS expects all its funded partners to use the IMOS logo
on IMOS-related records in their local GeoNetwork, and
IMOS then harvests these records.
Some of the partners create IMOS records as well as records for other stakeholders.
The only way that they can currently "assign" an IMOS logo to a subset of their metadata is to run 2 "internally accessible-only" instances of GeoNetwork, which they "harvest" into their sole "externally-accessible" GeoNetwork instance.
IMOS then harvests these into its own "central" IMOS GeoNetwork.
A separate project (AODN) uses Geonetwork too. The AODN GeoNetwork harvests from lots of catalogues, including the IMOS Geonetwork, and the IMOS "partner" instances of Geonetwork. In that process, an entirely different logo can be assigned to the IMOS records.
(not ideal)
IMOS "partner"'s Geonetworks are also harvested by 2 different national' umbrella catalogues, one of which is non-Geonetwork and uses OAI. Because the IMOS records are only a subset of the partner's GeoNetwork, the IMOS 'specificity' is lost. Currently, that harvester has no means of "knowing" the provenance of a harvested record, nor whether the record has been converted to another metadata profile, etc.
To meet their 'business needs' the 'national' harvester actually converts and subsets the harvested metadata. These records are then harvested by other harvesters.
etc
As part of the solution, BlueNet developed the "point-of-truth metadata url" (which we use within the ISO19115-"Marine Community Profile" and is in the BlueNetMEST). This is auto-generated and provides a direct link back to the original version of the record, in its original GeoNetwork instance.
However, its now becoming important to provide a harvesting and "metadata conversion" history and provenance, and a means for people (including metadata creators, metadata harvesters, metadata converters) to manage this better.
Could some of this be built into the MEF?
(I expect some of this can also be addressed by improving the metadata standards, however a metadata-independent solution would be more speedily achieved)
Kate Roberts
eMII, IMOS (Integrated Marine Observing System)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On 22/10/2010 10:48 PM, geonetwork-devel-request@lists.sourceforge.net wrote:
> Send GeoNetwork-devel mailing list submissions to
> geonetwork-devel@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
> or, via email, send a message with subject or body 'help' to
> geonetwork-devel-request@lists.sourceforge.net
>
> You can reach the person managing the list at
> geonetwork-devel-owner@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of GeoNetwork-devel digest..."
>
> Today's Topics:
>
> 1. [GeoNetwork opensource Developer website] #358: GROUP and
> CHOICE element handling. (GeoNetwork opensource Developer website)
> 2. [GeoNetwork opensource Developer website] #359:
> Administration / Logo manager
> (GeoNetwork opensource Developer website)
> 3. CFV / Logo manager (Francois Prunayre)
> 4. Re: CFV / Logo manager (jose garcia)
> 5. Re: CFV / Logo manager (andrew walsh)
> 6. Re: CFV / Logo manager (Francois Prunayre)
> 7. Re: [GeoNetwork opensource Developer website] #343: CSW /
> iso19110 / exception when requesting ISO19139 output
> (GeoNetwork opensource Developer website)
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America contest
> Create new apps& games for the Nokia N8 for consumers in U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
>