Ticket #621 (closed task: fixed)

Opened 14 years ago

Last modified 13 years ago

[M] Example for inclusion of Numsim/xlink fields in DPT

Reported by: selatham Owned by: lawrence
Priority: required Milestone: PROD Step2
Component: MOLES Version:
Keywords: NumSim Cc: rkl


Produce example MOLES amendments to DPT object to allow xlinking to a 'Codebase' type Numsim document. Do for next meeting 11thJan.

Change History

comment:1 Changed 14 years ago by selatham

  • Keywords NumSim added; Numsim removed

comment:2 Changed 14 years ago by lawrence

  • Milestone changed from MeetingsJan2007 to System Integration

comment:3 Changed 14 years ago by selatham

  • Owner changed from ko23 to lawrence
  • Milestone changed from BETA to Reporting and Futures

comment:4 Changed 14 years ago by selatham

  • Milestone changed from Reporting and Futures to PROD Step2

Bringing forward. Bryan looking at this. May need addition to moles schema.

comment:5 Changed 14 years ago by lawrence

  • So where do we do this? We should do it in the

element of the schema. This is currently an "empty complexType". It should become an online reference type. This requires a minor schema change that shouldn't impact on anything else, because noone has populate this. Something like:

<xs:element name="dgModel" type="moles:dgOnlineReferenceType" minOccurs="0" maxOccurs="1">

(Does anyone believe we should do anything internally in MOLES any longer?)

  • What should such an online reference actually look like? An example:
            <name> A description of the ERA40 model </name>
            <uri> http://glue.badc.rl.ac.uk/view/badc.nerc.ac.uk__NumSim__blah </uri>
           <dgValidTerm> NumSim model description </dgValidTerm
           <dgValidTermID> 10 </dgValidTermID>

... but I don't know how to point to the listid itself, and the vocabserver, from within MOLES? Why is there redundancy?(I would have put a citation class in here, but I don't think the MOLES citation class should differ from the ISO19139 citation class, and it should be replaced before it's used in anger).

  • We need to add NumSim into the appropriate vocab server list.

comment:6 Changed 14 years ago by lawrence

See also ticket:830

comment:7 Changed 14 years ago by lawrence

  • Owner changed from lawrence to selatham

comment:8 Changed 14 years ago by selatham

  • Cc rkl added
  • Owner changed from selatham to lawrence

Example with vocab ref in as follows. Roy can you please check. Am I OK to use the abbreviated term as the dgValidTerm? It is the same logical thing that the ParentListID+TermID point to, and it's more practical for display.:-

        <name> A description of the ERA40 model </name>
        <uri> http://glue.badc.rl.ac.uk/view/badc.nerc.ac.uk__NumSim__blah </uri>
	<dgValidTerm>NumSim Page</dgValidTerm>

comment:9 Changed 14 years ago by rkl

Hi Sue,

It doesn't really make a whole lot of difference whether you use the abbreviated term or the full term. You just need to be aware that there is a high risk of the abbreviated term expanding during any ingestion/re-export process. The reason for this is that systems may opt just to store the TermID and populate dgValidTerm dynamically from the Vocabulary Server on export and the most likely field for them to use is the term.

What does matter is that the ParenListID needs to be versioned - either use  http://vocab.ndg.nerc.ac.uk/term/N041/2 or  http://vocab.ndg.nerc.ac.uk/term/N041/current. Otherwise it's impossible to build the term URL.

comment:10 Changed 14 years ago by lawrence

I've modified the schema accordingly, in subversion, and on glue. (changeset:2813)

comment:11 Changed 14 years ago by lawrence

However, once I did that, Sue thought some more about it, and recommended we leave dgModel as a flag, and use the online reference type in the description. Consumers of the moles document can look for the flag, and then use the reference class to find numsim (and other) model descriptions ... see changeset:2818

comment:12 Changed 13 years ago by lawrence

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