Routes (or Site Map)

In the hopes of preventing a spaghetti mess, it might be best to lay out the routes and use them as a kind-of checklist to work through.

basic app routes

• /
  • home page; intro text-block + card-catalog image
• /login
• /logout

collections

• /:collectionId
  • collection home; display a thumbnail grid?
• /:collectionId/import
• /:collectionId/export
  • import/export collection metadata
• /:collectionId/edit
  • edit collection metadata (currently: name, description, schema metadata)
• /:collectionId/works/:workId
  • edit an item w/in a collection.
• /:collectionId/works/bulk
  • maybe just /:collectionId/bulk-edit ?
  • table-edit mode

works

• /works
  • works home; use Sufia's recent updates/additions api to display works viewable by user
• /works/:workId
  • edit a work outside of the collection scope. maybe we can include a originCollection field, or something like that, if the WorkEdit component's this.props.params.collection property is an empty object (signifying view is outside of collection scope`
    • though, how will we access the schema metadata?
      • maybe we make an api call to retrieve the collection data anyway, based off the originCollection (or whatever) property, but because this view isn't wrapped in the CollectionWrapper component, the collection header/links won't be displayed
• /works/:workId/files
  • file management (sufia uses file_sets on a work level)

search

• /catalog
  • should follow sufia's search functionality pretty closely. items might be edited within modals using react-modal wrapping WorkEdit.

vocabulary management

• tbd, something like /vocabulary as a base root

user management

• tbd
• /users
  • view a list of users to edit
• /users/new
  • add new user
• /users/:userId
  • edit/delete a user