Ticket #879 (closed task: worksforme)

Opened 14 years ago

Last modified 14 years ago

[M] non-breaking spaces shown as   in Discovery

Reported by: selatham Owned by: lawrence
Priority: critical Milestone: Replace Metadata Gateway
Component: discovery Version:
Keywords: Cc:

Description (last modified by lawrence) (diff)

e.g.  http://ndgbeta.badc.rl.ac.uk/view/www.npm.ac.uk__DIF__data_entity.105 The   are appearing in the parameter names. This seems to happen wherever there are parameter names with spaces. The corresponding browse record does not have the nbsp's  http://wwwdev.neodaas.ac.uk/projects/ndg/view/www.npm.ac.uk__NDG-B1__data_entity.105 This seems to indicate that it's something happening either at ingest into mini-moles or specifically when displaying discovery records. I'll investigate ingest. Bryan - is displaying in browse any different to discovery?

Change History

comment:1 Changed 14 years ago by lawrence

Yes, it is done differently, and you've given me a hint as to what the problem may be ... do investigate ingest, and I'll look at my bit ...

comment:2 Changed 14 years ago by lawrence

  • Description modified (diff)

comment:3 Changed 14 years ago by lawrence

  • Owner changed from lawrence to selatham

Well, exactly the same code fragment is used to display the parameters in the template ... so suspicion had better move back to the python class, or indeed, the ingestion ...

Also, why are NO BADC parameters visible in discovery ... but they are visible in browse, but there are no spaces in the parameters visible in the B records ... (and that's coming from the XML).

I reckon that's related.

comment:4 Changed 14 years ago by selatham

  • Owner changed from selatham to lawrence

The lack of spaces in BADC parameter names is because they don't have spaces as stored in the postgres catalogue. Bryan - you said you had an idea how to solve the display? So I'll pass back to you for now.

comment:5 Changed 14 years ago by lawrence

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

Changeset:3086 has a fix which should sort out the DIF display, but I'm not sure why it was happening in the first place ... (and not in browse).

Note: See TracTickets for help on using tickets.