Ticket #694 (closed issue: wontfix)

Opened 12 years ago

Last modified 12 years ago

[M] Late binding in MOLES

Reported by: lawrence Owned by: lawrence
Priority: discussion Milestone: Reporting
Component: MOLES Version:
Keywords: Cc:

Description

Two interesting cases:

  1. The deployment appears to be an integral part of records in MOLES.
    • Should it not be a document in it's own right? That would allow late binding of data entities to new activities etc without having to edit all the parts of the deployment.
  2. We currently have services as part of metadata records, yet we know that's not the way to do it. If we had service description records in MOLES, and we had service binding records, then we'd have the ability to late bind services to metadata as well (based on granule feature types).

Maybe both can appear in a future version based on ebRIM registries, but I wonder how hard one or other would be to do in a version of MOLES? (Not for NDG2 obviously).

Change History

comment:1 Changed 12 years ago by ko23

Interesting point.

While a deployment is always a dependent entity, it could well, when fully developed, be worth a separate document. But we're a loooooong way off justifying trying to implement this, given that MOLES is only just now starting to get properly tested.

comment:2 Changed 12 years ago by selatham

  • Owner changed from ko23 to lawrence

comment:3 Changed 12 years ago by selatham

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

Not in NDG2.

Note: See TracTickets for help on using tickets.