Ticket #184 (closed issue: wontfix)

Opened 15 years ago

Last modified 14 years ago

[m] massive numbers of related entities in moles

Reported by: lawrence Owned by: ko23
Priority: required Milestone: PROD
Component: MOLES Version:
Keywords: MOLES_Portal,StubB Cc: lawrence


Where we are going to have a long list of related entities there may be issues with the way we do xquery. How should we order them?

Change History

comment:1 Changed 15 years ago by lawrence

  • Component changed from T01_Discovery to T07_MOLES

comment:2 Changed 15 years ago by spascoe

Relates to look & feel of whole system.

comment:3 Changed 15 years ago by ko23

Negotiation required. Optimisation will depend on how people wish to display the entities, so it's best to start arm-wrestling from there. Also, there's the question of what "massive numbers" is: we need to generate some and test.

comment:4 Changed 15 years ago by selatham

You can already see that some of the MOLES objects returned from deployments will be duplicates. e.g. Observation station Macehead has many deployments and Activity EAE is mentioned in a couple.  http://glue.badc.rl.ac.uk/cgi-bin//browse.py?uri=badc.nerc.ac.uk/obs1 So if we didn't list them twice this would probably help matters. Whether this rationalisation of duplicates should happen in the XQuery or the interface needs to be discussed.

comment:5 Changed 15 years ago by lawrence

  • Keywords MOLES_Portal,StubB added; MOLES_Portal removed
  • Priority changed from critical to required

comment:6 Changed 14 years ago by lawrence

  • Milestone changed from BETA to PROD

comment:7 Changed 14 years ago by lawrence

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

Well, this has been subsumed into other activities for now ... so we can close the ticket.

Note: See TracTickets for help on using tickets.