Ticket #384 (closed task: fixed)

Opened 15 years ago

Last modified 15 years ago

[M] MOLES dgDataGranule re-design

Reported by: selatham Owned by: ko23
Priority: critical Milestone: MOLES 1.2.5
Component: MOLES Version:
Keywords: GranuleSummary Cc:


Following resolution of issue #382, a dgDataGranule needs it's own spatio-temporal atrributes, access constraints, title(short-name), features(like dgDataType). Kev to come up with proposal by w/e June 12th.

Change History

comment:1 Changed 15 years ago by selatham

  • Milestone changed from PreAlpha to MOLES 1.2.5

comment:2 Changed 15 years ago by selatham

Bryan made the point that the Parameter Usage Vocabulary terms should also appear in MOLES, but under a granule. Therefore they are available for MOLES browse, but would not be used for Discovery.

So they need to be in the cross-over bit (S for Summary) with CSML.

comment:3 Changed 15 years ago by lawrence

Should also include access constraints (which I think it does already, but just flagged here). (See ticket:348, which has been moved here. Note that csml already has access constraints).

comment:4 Changed 15 years ago by lawrence

  • Keywords GranuleSummary added
  • Milestone changed from MOLES 1.2.5 to MOLES 1.3

The redesign is in draft ndgmetadata1.2.5, the key elements of which are in this

However, this uses the dgParameterType, which demands a choice of dgValueParameter,dGrangeParameter,dgEnumerationParameter, and dgParameterGroup. For a dgGranule, BNL thinks this section should be ommitted, so we can't complete this until we solve ticket:460.

This ticket can be closed when we know that all the content in the dgGranule can be generated from a CSML document, so the last step will be to pass it to Dom.

comment:5 Changed 15 years ago by ko23

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from MOLES 1.3 to MOLES 1.2.5

See implementation. ACW.

Note: See TracTickets for help on using tickets.