Infrastructure Requirements

Questions

Need to consider both functional and technical requirements and how they interconnect

Functional requirements – what needs to be decided

What type of editor/formatting options will be required
- Strategic Partners will be looking into this (see Web Content Guidelines working group)
How does data need to be inputted for individual content types
- This will likely require a set of templates, with descriptions.
- We will be starting with Service, Space, Building, Groups, and Persons in thinking about content.
How should the metadata content be rendered on the front-end user interface
- Need to consider both full and partial views for each entity
- Need to consider aggregate pages of information (ex. library hours)
What additional workflow management features are required – ex. approval queues, versioning, etc.
- Distinguish "Must Have" vs. "Nice to Have" – will need to follow up with the Web Advisory group on this
What does the admin user interface need to look like

Technical requirements – what needs to be decided

How to build relationship between different entities (and support broader data model)
How to have consistent styling across content types
- Ideally, we will reuse as much of Blacklight as possible.
Eventually, how do we incorporate other library systems, such as Springshare products (LibChat, LibAnswers, LibCal) and Wordpress blogs