Ticket #667 (closed task: fixed)

Opened 14 years ago

Last modified 12 years ago

[M] Parse localID for characters which need escaping(exist rejects)

Reported by: selatham Owned by: sdonegan
Priority: required Milestone: Reporting
Component: discovery Version:
Keywords: WS-Discovery2 MDIP Cc:


In ingest process, do something about localIDs which have chracters which need escaping. How do we match up with filenames?

Change History

comment:1 Changed 14 years ago by ko23

Which characters does eXist reject for which format?

comment:2 Changed 14 years ago by selatham

  • Priority changed from critical to required
  • Status changed from new to assigned
  • Milestone changed from BETA to Replace Metadata Gateway

comment:3 Changed 13 years ago by selatham

Am having to deal with colons specifically - exist really doen't like these, but Discovery DPs really seem to like them in their Entry_ID fields! NDG providers have their colon separaters turned into double-underscore if they aren't already. Will have to change non-NDGers colons to something else, probably a hyphen.

comment:4 Changed 13 years ago by selatham

Colons sortedat ingest. What other characters are going to cause problems? List them. Change all to hyphens?

comment:5 Changed 13 years ago by lawrence

  • Status changed from assigned to new
  • Owner changed from selatham to sdonegan

comment:6 Changed 12 years ago by sdonegan

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

Not using exisit anymore as all ingested records held as text fields within postgres - so fixed.

Note: See TracTickets for help on using tickets.