Ticket #317 (closed task: fixed)

Opened 13 years ago

Last modified 11 years ago

[C] Liaison with WDCC Max Planck as a Discovery Provider

Reported by: selatham Owned by: sdonegan
Priority: required Milestone: NDG3
Component: discovery Version:
Keywords: metafor Cc:

Description (last modified by selatham) (diff)

Work with Hans Ramthun from WDCC Max Planck so that they can become part of NDG as a Discovery Provider. Possibly a full DP in future. Is also a GO-ESSP group target.

Change History

comment:1 Changed 13 years ago by selatham

  • Priority changed from blocker to required
  • Status changed from new to assigned

Cannot harvest from their oai for obscure reasons. They have become anxious. Therefore attempting to take their records and manually add to our system so that they can assess how they behave/what they look like within the NDG portal. This has highlighted another problem with ingesting large amounts of records - assigned to another ticket. However, must solve this problem with harvesting.

comment:2 Changed 13 years ago by selatham

Have ingested WDCC records to glue discovery by by-passing OAI. Still haven't solved harvesting problem. BODC can harvest OK.

comment:3 Changed 13 years ago by selatham

WDCC are using:- OAI 2.0.9.3 + tomcat 5.5.12 compatibility package, Java 1.5)

BODC are using:- OAI = 2.0.9v Tomcat = 5.0.28 Java = 1.4.2

comment:4 Changed 13 years ago by selatham

Replaced (manually)their original 1700 records with their new 42 DIFs. In both glue and superglue eXist databases now. They've got their related_urls sorted now, so they go to a wdcc dataset page where an 'experiment' is described and various subsets of data related to that are shown.

comment:5 Changed 13 years ago by lawrence

Can we harvest yet?

comment:6 Changed 13 years ago by selatham

Can we harvest yet?

No. Was going to raise as separate ticket. Seems to be problem at our end. May need to install latest version of DLESE OAI. Have heard of other issues with DLESE stuff from ECMWF and CLADDIER users. So it may be 'OAI s/ware issues'.

comment:7 Changed 13 years ago by lawrence

  • Milestone changed from ALPHA to SytemIntegrationOctober2006

comment:8 Changed 13 years ago by selatham

Upgraded Dlese jOAI (as well as tomcat,java). Still can't harvest from WDCC properly. BODC can harvest them OK. Can only think that it's something to do with some content in their records and maybe our xml validator. Met with Hans etc at Max Planck Sept 14/15th. Discussed these problems as well as their ISO19115 records. Hans will create a set of their ISO records at the 'experiment' level. This is the same level as the DIFs we were getting. We can then look at the content, compare with the DIFs and attempt harvesting.

comment:9 Changed 13 years ago by selatham

  • Keywords GO-ESSP added
  • Description modified (diff)

comment:10 Changed 13 years ago by selatham

  • Milestone changed from SystemIntegrationOctober2006 to BETA

No progress since last report. Need to contact Hans.

comment:11 Changed 12 years ago by selatham

  • Milestone changed from BETA to Replace Metadata Gateway

comment:12 Changed 12 years ago by lawrence

  • Keywords club added
  • Component changed from T08_International_Collaboration to DiscoveryService

comment:13 Changed 12 years ago by selatham

  • Milestone changed from Replace Metadata Gateway to PROD Final

comment:14 Changed 11 years ago by lawrence

  • Keywords DiscoveryService added; club GO-ESSP removed
  • Component changed from DiscoveryService to discovery

Moved from DiscoveryService? component to discovery as part of NDG2 cleanup

comment:15 Changed 11 years ago by lawrence

  • Keywords metafor added; DiscoveryService removed
  • Status changed from assigned to new
  • Owner changed from selatham to sdonegan
  • Milestone changed from NDG2 Cleanup to NDG3

Can you change this to some sort of smart objective, and note link to ticket:599!

comment:16 Changed 11 years ago by sdonegan

  • Status changed from new to closed
  • Resolution set to fixed

Records harvested fine now from wdcc ( think they changed their provider setup.)

Note: See TracTickets for help on using tickets.