...
Individual entity types will have additional fields specific to the type. See the Entity Metadata Descriptions document linked above for the full list of the metadata fields. Also, see below for specifications regarding each entity type.
Event
- Event entities will be time-stamped and be divided into current and future events and past events.
- For all past events, we will need the ability to optionally upload a video of the event.
Form
- While not an entity in true definition of the term, we will need to have a space on the website for forms.
- All sort of things use forms, from requesting new book purchases to 3D prints to feedback.
- Forms will need to have an email notification component so that the form can be directed to the proper person/group.
- Sometimes multiple persons/groups may be a recipient depending on an option checked off by the person completing the form (3D printing is an example of this).
...
Speaking of PDFs, right now, there is of org charts for each department within the library that are all PDFs. In theory, once we have all of the person entities filled out in the website, we would be able to dynamically generate org charts based on metadata.
...
The library hours are a very popular component of the website and are tied to several of the entity types. Currently, hours are input through a Google Spreadsheet managed by Sheryl. Drupal calls the spreadsheet and displays the hours in predefined spots on the website. Ideally, we would keep the workflow the same with Sheryl continuing to use the Google Spreadsheet.
Libraries
The libraries are as follows:
...
Similar to the Blog content, we eventually want to render the content from LibGuides within the CMS display. However, for now, links to LibGuides will be sufficient.
Events
All event information is pulled from the university's central event calendar based on tags and displayed in a page on the CMS.
Hours
The library hours are a very popular component of the website and are tied to several of the entity types. Currently, hours are input through a Google Spreadsheet managed by Sheryl. Drupal calls the spreadsheet and displays the hours in predefined spots on the website. Ideally, we would keep the workflow the same with Sheryl continuing to use the Google Spreadsheet.