2016-09-01

• Today we discussed the wireframe and work flows of the editorial interface in Charon.
• Our first assumption is that we start with a "project" with goals, workflows, and items, as well as a registered project staff.
• The first screen an editorial user would see would be the "deposit" screen, with the addition of very minimal metadata and a suggested collection.
• There is then a dashboard for each project a user is on, where they can accept, reject, or work on various tasks and items.
• Some procedures will be automatically done on accepted documents that elect for them, like the generation of a TEI skeleton and OCRing.
• There would be different ways to assign tasks - through the administrator only, project managers delegating tasks, or user choosing their assignments, or users choosing tasks, based on the workflows set up for the project.
• Once all tasks are done, an item could be exposed through CERES.
• Charon would be exclusively for registered project team members.