You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

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
    • 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
  • No labels