...
- 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 definitions based on Citation Schema.
- Authorization issues...
- how do we keep non-University members from accessing licensed metasearch engines?
- MetaLib Repository OSID Implementation
- 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...
...
- Assets/Records/Parts
- Configuration
- perhaps use a Java Object (such as
org.osid.OsidContextor ajava.util.Propertiesobject forRepositoryManager.assignConfiguration())to maintain and modify configuration settings. - Use a text file to configure what kinds of tags you want to identify and values you want to store from the metadata being returned by metasearch engines. The format for this file could be structured like an XPath Query to easily get to specific elements within an XML file.
- perhaps use a Java Object (such as
- Search Syntax (CQL?)
- others... (continue to add to this list)
...