Meeting Notes
Common Services
...
Following are notes from the meeting. Colored text indicates a response (answer to a question, decision change, etc.) to preceding, non-colored text.
Where to go from here
- Discussion regarding "2 jars + common services" versus "1 giant jar" implementation model.
- For now, stick with "2 jars + common services"
- This way, we can concentrate on a "fresh" implementation, while at the same time maintaining what we've already got.
- Assets/Records/Parts definition
- Create all new Assets, Records, Parts
- Authorization issues...
- how do we keep non-University members from accessing licensed metasearch
engines?
- how do we keep non-University members from accessing licensed metasearch
- MetaLib
- Assets/Records/Parts
- session management
- asynchronous search with X-Server
- pagination
- experiment with custom record presentation
- setting up a testing framework (JSP/Servlet)
- SingleSearch
- Assets/Records/Parts
- session management
- asynchronous search with Web2
- weak data...
Common Services
- Assets/Records/Parts
- Configuration
- Search Syntax (CQL?)
- others... (continue to add to this list)
Potential Questions for Jeff Kahn
- What is the purpose of creating a new Repository each time a search is
conducted? - Authorization within OKI?
- What is it we can change/not change?
- Repository Federator
- SRW Repository Implementation
- Do we have to use RepositoryManager.properties (resolution conflict)?
- OSIDRepositoryTool Servlet
...