General Notes

(based on discussion with Chad, David, and Emily)

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

Functional requirements – what needs to be decided 

• What type of editor options will be required – ex. html styling
• How does data need to be inputted for individual content types and
  • 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 is the metadata content rendered front-end user interface 
  • Consider both 
• What additional workflow management features are required – ex. approval queues, versioning, etc.
  
  • Distinguish "Must Have" vs. "Nice to Have" 
• What does the admin look like

Technical requirements – what needs to be decided

• How to build relationship between different entities (and support broader data model)
• How have consistent styling across content types
  • Ideally, we will reuse as much of Blacklight as possible. 

Developer: Steven Ng

Cynthia's Notes (Work in progress)

Entities

The traditional CMS portion of the library web environment will be built around individual entities. Each entity will have its own page. Additional pages may contain lists of entities. Entities will be categorized with a type. Each entity type will have a similar page template that include visible data fields and invisible metadata fields. 

...