[M] Bug in Activity stub b xquery?

[lawrence]

The metadataid element is surrounding nearly the whole record: see the attached example. Is this content or the xquery?

[lawrence]

Example of stub-b returned

[ko23]

A misplaced bracket, so I'll fix it IDC.

[lawrence]

Actually, there's something wrong with the Activity one too; it seems to generate an infinite loop on chinook ...

(Can you do something about these in the back of your meeting, it's a blocker for any GUI development of browse, i.e. for BETA).

[ko23]

Oh go on, as it's you...

Seriously, from the quick tests I've done, it looks like the ObsStn? one is the only one with a problem, so it's now fixed.

As there aren't any activities in the /db/discovery backup from glue, could you make the chinook version available for me to look at?

[lawrence]

Example activity from chinook

[lawrence]

As you can see I've added an activity to this ticket, and changed the ticket name. NB: could the activity_activity be the problem?

[selatham]

Some badc records are actually called 'activity_activity_xxxx'. This is due to badc originally making ids activity_xxx when generating initial activities in the new catalogue. Then a prefix of 'activity' gets added giving the external localid activity_activity_xxx. Newer ids will look like activity_nnnnnn, where nnnnn=pure numeric.

[ko23]

Loaded activity_activity_chablis.xml into my testdb, and xquery ran OK. However, I note that there's 25 deployments in there, and I don't seem to have access to the relevant des, dpts, and obsstns. It seems that, if there is a problem, the problem is going to be in the resolution of the deployments.

Hence, I repeat the request that the relevant data is made available.

[ko23]

Chablis StubB (note that error elements are added by XQuery: perhaps we should talk about about error condition cases and structure to make life easier at the front end?)