Review IS&T Service Portfolio requirements: document can be downloaded from here
Discuss options for housing the IS&T Service Portfolio based on requirements:
- drupal
- PRO: supports existing workflows
- PRO: relational database
- PRO: flexible (forward thinking)
- PRO: we can "throw it away" if needed (open source)
- PRO: easy to extract information from tables
- PRO: 3rd party resources are available to help build (need funding)
- PRO: Systems Engineering will be developing service offering
- CON: currently no robust support model or expertise, but it is in process (see above)
- Hermes (Confluence)
- CON: needs to upgrade to 3.4 (search customization makes this complicated)
- CON: no relational database
- CON: does not support work flow
- Excel
- CON: flat spreadsheet, no relational database
- Access
- CON: no support
- FileMaker
- CON: very limited support
- 3rd Party Solutions
- CON: need time to do discovery
- CON: would have significant impact on time line
- CON: would also have unforeseen impacts on Service Catalog, which is beyond scope of project
Next steps:
- Pat will talk with Rich regarding time line and support model for drupal service, if feasible
- Pat will discuss with Barbara and additional funding needs based on conversation with Rich
Next team meeting scheduled for Thursday February 24th at 1pm in N42-202. Depending on technology next steps cited above, we may defer meeting as a team and sub groups can use the time to work on other project deliverables.