by Jon Griffin
I. Essentials
- There is no user accessible directory
- There is no sub-site admin accessible diretory
- Requirements document: Requirements
- ER diagram:
II. Introduction
Reference data is often overlooked in the rush to get coding. In reality, much of ….
III. Historical Considerations
Before the existence of acs-reference, the ACS required that you preload some tables in a script to get some basic reference functionality. There were many problems with this:
- No easy way to find out what reference data even existed.
- No way to find out how old the data was.
- No way to find out where that data came from.
- Very US/English slant on the data.
IV. Competitive Analysis
The only real competition is internally developed solutions.
V. Design Tradeoffs
Primary Goals
- This system was designed with maintainability and reusability as its primary goals. By wrapping a layer around all of the reference tables we have increased the maintainability immensely.
- Another goal was to bring together many different types of data and present them in a logical fashion. It was amazing how little of this data is available on the internet in a database friendly form.
Performance
When updating the reference tables their is overhead due to the fact that the table is registered with the repository. This should rarely occur anyway as the tables are only added once. By not having the actual data itself in the acs-object system, subsequent additions and deletions to the reference tables themselves are unaffected by this overhead.
VI. API
VII. Data Model Discussion
VIII. User Interface
Their is no end user interface. There will
IX. Configuration/Parameters
None
X. Future Improvements/Areas of Likely Change
A server based update mechanism will be supported. This will allow for tables to be updated (and preferably diffed) instead of being reloaded with a package upgrade. An interface to produce xml/csv from the reference data would be a nice service to the community (allowing legacy applications a way to import this data).
XI. Authors
XII. Revision History
$Log: design.adp,v $ Revision 1.1 2003/03/24 06:35:22 jon initial cvs Revision 1.1 2001/04/28 05:10:23 jon initial version
Related posts:
- Trying to Design a Business Logo One thing that makes your business standout from the crowd...
Related posts brought to you by Yet Another Related Posts Plugin.