...
4:45-5:00: Wrap up, next steps
...
Agenda ideas, to be inserted:
More discussion of query or export or? for supporting things like public browsing.
Possibilities:
- Use the application layer to map services into a data model for the public browser
- Build new services that aggregate things for common cases
- Use a data warehouse model that exports CSpace data to a custom DB just for the browser.
Think about issues around media reuse sharing.
Managing documentation for current deployments
For sharing of experience, pain, etc.
Integration with external systems
Regular, automated import or export from/to another system
Linking to DAM systems, etc. for media management.
Fetching data, sending data, upon user invocation for specific tasks (placename resolution, mapping, query or export to genomic DBs, etc.)
Adding constraint logic on entered values
- In the UI vs. in the services (user entry constraints, vs. data constraints including on import)
- Code development and maintenance in Javascript vs. Java
BOF (birds of a feather) sessions on specific topics
Do we want to consider this, or should we keep discussions global with everyone?
Specific topics might include:
- Custom widgets, e.g., modifying structured date behavior
- Citation authority requirements
- Concept Authority for various authorities
- CDWA (lite) mapping