Build a Terminology Service
Build a Terminology Service in OSHIP. This blueprint will be broken down into smaller tasks as the requirements become better known. The terminology service is described in the Support IM document.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Diego Manhães Pinheiro
- Definition:
- Approved
- Series goal:
- Accepted for 1.0
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Tim Cook
- Completed by
- Diego Manhães Pinheiro
Related branches
Related bugs
Sprints
Whiteboard
At the moment, the terminology service doesn't have an implementation available to make queries by their terminology names, catch code sets, etc. The actual API design doesn't allow add more terminologies without change the main code. This a important point because there are some different terminologies set to the OSHIP already.
In a first time, the terminology service could read XML files and then match the correct code, to create a simple way to solve the problem.
After that, if a performance problem appeared, approaches like use a indexing mechanism and pre-load all new terminology every time the system starts up could be useful in order to improve the performance.
The Zope Component Architecture(ZCA) and the data structures provided by the ZODB, such as BTree, could help to achieve the extensibility and performance goal, respectively.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
