Difference between revisions of "Code Discussion 2008-10-13"
Jump to navigation
Jump to search
m (→Implementation) |
(→ToDo) |
||
| Line 23: | Line 23: | ||
* Unit and integration tests | * Unit and integration tests | ||
* Create, update and delete methods | * Create, update and delete methods | ||
* Define and implement harvesting or | * Define and implement harvesting or automated update mechanisms | ||
* Check for JS, SQL, etc. injection | * Check for JS, SQL, etc. injection | ||
* Data Management | * Data Management | ||
** Currently used DC data at its limits to describe model | ** Currently used DC data at its limits to describe model | ||
** Unique identifier issue | ** Unique identifier issue | ||
Revision as of 12:50, 13 October 2008
ControlOfNamedEntities Service (CoNE v.1.0.0)[edit]
Purpose of the code discussion[edit]
- Inform about the service
- Find weaknesses in the current implementation
- Generate ideas for further development
Purpose of the service (v.1.0.0)[edit]
CoNE shall deliver information out of a list (model) of comparable objects, e.g. journals, languages, authors. Clients (human or machine) shall have the opportunity to search for objects to select exactly the object they were looking for (e.g. autosuggest). They than shall be able to deliver more detailed information on this object.
Implementation[edit]
- [Current code]
- JQueryConeServlet implemented
- Currently used Querier: SQLQuerier pointing to Postgres database on zim02.gwdg.de
- Current models: Journals, languages (in en, de, fr). Author names coming soon...
- MVC? pattern
ToDo[edit]
- Look for a suiting triple store
- Unit and integration tests
- Create, update and delete methods
- Define and implement harvesting or automated update mechanisms
- Check for JS, SQL, etc. injection
- Data Management
- Currently used DC data at its limits to describe model
- Unique identifier issue