Enhance UI for Projects

[bryanrcarlson]

These are tasks / suggestions that were discussed during a presentation of how Projects were implemented in the latest dev build:

• Projects page (catalog/projects)
  • Should render projects with markdown instead of simple text. Also set a max height and either use a scroll bar or a "more..." link to expand
  • Show number of datasets per project; don't worry about performance until it becomes an issue. Can add a field like datasetCount in catalog.json that is populated by the collator
• Strip whitespace when assigning the relationship between projects and datasets via LINQ to avoid input issues
• Insights page
  • Show datasets without projects and/or projects without datasets to highlight potential issues
• Catalog page (catalog)
  • Remove tabs for Datasets, Variables, Projects. Instead, make them sub-items with each having their own url; this enables back button better
• Don't use .mippen; use .md files instead (this has been addressed between that meeting and this note)
• Create a project editor that is a markdown editor and allows downloading of the project file and loading (like the metadata editor)
  • Add the "Project" editor as a sub-menu to the current "Editor" nav menu. Also add a "Dataset" sub-item under the same parent that links to the current editor
• Consider a "Variable" tab in the Project-detail pages; this in addition to the current datasets that are listed