Questions
We need to clarify how much information is modeled as Location over time, and just what information is needed for the Movement as such:
- Does this capture the details of Transport (e.g., to note a transport company and their shipment information), or is that separate?
- We expect that there will be Insurance information tied to a Loan, but will there also be separate information tied to Transport/Movement?
What is the scope of a Movement that will be modeled by this service? Which of the following does it encompass?
- Exhibitions.
- Loans for exhibitions
- Other loans.
- Conservation activities.
- Changes of location within a museum.
Is the Movement Service a hybrid of a task service and an entity service? Does a calling application need to orchestrate the act of a movement, such as setting a new object Location, by calling multiple services (including this one), or does the act of creating a Movement entity also trigger a Location change? (This general question may also apply to Exhibition, Loan, and similar services.)
How should in-transit states, such as the transportation of a physical collections object via a postal or delivery service, or a courier, reflected in Movement and related services? (This may also include the need to reflect paperwork or electronic documentation related to the transportation in a Documentation service.)
For intra-museum moves, does there need to be some notion modeled within the CSpace system of what the minimum threshold is to trigger a Movement event, or is that purely up to the discretion of the system users? (That may be a silly question, but is asked here for completeness.)