Ticket #860 (closed defect: fixed)

Opened 14 years ago

Last modified 14 years ago

[D] Problems retrieving MDIP record

Reported by: lawrence Owned by: lawrence
Priority: critical Milestone: PROD Step3
Component: discovery Version:
Keywords: Cc: mpritcha


e.g. try  this link, which results from  this search.

This appears to be related to the URI itself: which has MDIP as the schema of the record, but NDG doesn't recognise MDIP as an *output* format for discovery ... if we want to have a D link understandable by NDG then it has to be a recognised NDG schema (at the moment DIF, maybe DC, and soon ISO).

How is this URI constructed? Did they produce it or did we?

Change History

comment:1 Changed 14 years ago by lawrence

  • Type changed from task to defect

comment:2 Changed 14 years ago by lawrence

Note that I have added a fix which means we should see the xml record pretty printed for records with mdip as the schema ... is that enough to make everyone happy in which case let's just close the ticket and forget about it ... (nb: in changeset:2846, not yet on glue)

comment:3 Changed 14 years ago by selatham

  • Cc mpritcha added
  • Owner changed from selatham to lawrence

Display of MDIP records through the normal Discovery portal method definately used to work OK. We will be completely unstuck when it comes to having mixed ISO and DIF. We had this cracked. The filename dassh.ac.ukMDIPMRMLN00100000036 is created when the record is ingested. MRMLN00100000036 comes from the identifier within the MDIP record:-


The repositoryid dassh.ac.uk comes from a config file. The scheme MDIP comes from the fact that I know I'm harvsting MDIP from dassh (config file again). The Moles record has the same filename and this identifier XML:-


What does the view service do with this? If it uses the WS back-end and asks for format=DIF then a Moles-to-DIF transform should occur and you can present as you do DIFs.

comment:4 Changed 14 years ago by lawrence

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.