We’ve been discussing different types of collaboration and the ways that projects can be set up, managed and sustained based on collaboration, partnerships and shared responsibilities. Using a project that you are either working on currently or one you would like to work on, create a collaboration document for your project. Your document must include a vision statement (what the larger goals of the project are), a code of ethics (expectations for behavior), a scope of work (what needs to be done), a set of roles and responsibilities (ie: project director, graphic designer, etc), and a timeline for production that includes various iterations, analysis, updates and launch date.
The Interactive Emblem: A Return to the Icon as Visual Mode
The twice-funded Emblematica Online project has done important work in digitizing renaissance emblem books for future scholarship. This work, however, deprives the icon in each emblem of its power to signify visually, instead transcribing attributes of the icon into language and metadata for purposes of digital archiving and curation. Our project seeks to demonstrate what an online portal for the discovery and study of emblem books–as well as other illustrated historical texts–might accomplish if it were not to compromise by remediating the icon into a linguistic form.
Code of Ethics:
- All collaborators will be granted full participation and a vote in regular business meetings, regardless of position.
- All kinds of work on a project are equally deserving of credit (though the amount of work and expression of credit may differ). And all collaborators should be empowered to take credit for their work.
- All collaborators will each be featured on the final website, along with a link to their professional website and contact information, arranged in a grid format according to position.
- If the project is funded, all collaborators will receive equal hourly compensation for their work up to a weekly maximum, regardless of position or type of work. The exception is Project Directors, who will receive a set stipend.
- All collaborators will treat each other with respect. Feedback should be constructive and kind.
- All collaborators must meet the deadlines set at regular business meetings. Failure to meet more than two major deadlines will result in one’s removal from the project.
Roles and Responsibilities
- Project Director(s) facilitate communication and set goals, adhering to the vision statement for the project. Directors call business meetings, handle grant funding, and elaborate the theoretical underpinnings of all project work.
- Web developer(s) provide the end-user experience for the project. This includes hosting the archive and designing its interface.
- Programmers code the archive and interactive emblem experiences.
- Researchers choose appropriate emblems for the project, negotiate rights to scans, gather all scholarly resources available on said emblems, and place them in the drop box for digitization.
1/30/18 – Initial business meeting. From this point on, business meetings happen in the last week of every month.
2/20/18 – Archive alpha work begins.
6/1/18 – Archive alpha functional. Researchers hired to begin populating archive alpha.
6/15/18 – Archive beta work begins.
8/15/18 – Archive beta functional. Researchers trained in UI, transfer emblems from alpha to beta. Quality testing begins.
10/15/18 – Researchers finish populating the archive. Join quality testing.
12/15/18 – Official launch.