Difference between revisions of "DSG DRS Pilot Project Workflow"
(9 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | <!--timeframe? projects get a year of initial support | ||
+ | content review and prep will take time, things need digitizing, need resources to digitize them. | ||
+ | end of fall would be great to have a partial or whole ingestion, training can also be done at this time | ||
+ | spring would be wordpress rollout | ||
+ | we will mark what is time intensive eventually - metadata, | ||
+ | |||
+ | the dissemination of info isn't quite settled yet, such as how meeting structures will be set up. | ||
+ | populate stuff with more information - feature tracking | ||
+ | |||
+ | some things need more info (outreach) | ||
+ | --> | ||
== Introduction== | == Introduction== | ||
− | + | The CERES: Exhibit Toolkit is a WordPress plugin and theme developed by DSG staff. CERES is used to create websites that dynamically integrate images, text, video, and other digital materials into complex scholarly narratives and exhibits. Digital materials may be drawn from Northeastern’s Digital Repository Service (DRS) or the Digital Public Library of America, and potentially from other open repositories as well. Accepted projects will partner with the DSG and DRS teams to use CERES to securely store their project materials in the DRS and create a customized WordPress site to publish those materials on the web. | |
− | == Preliminary Meetings== | + | ==Project Work== |
+ | |||
+ | ===Preliminary Meetings=== | ||
*Attendees: Sarah, Amanda, Jim (DSG), project stakeholders, library liaison(s) | *Attendees: Sarah, Amanda, Jim (DSG), project stakeholders, library liaison(s) | ||
*Agenda: Introduce DRS to projects, get more information about project scope and intentions, discuss location of project data and state of data (digitized, not digitized, format, etc.), delegate points of contact between project and DSG (Jim / Coordinator on DSG end, Project contact determined by project), discuss next steps involved in Content Review for project and DSG, email summary of meeting. | *Agenda: Introduce DRS to projects, get more information about project scope and intentions, discuss location of project data and state of data (digitized, not digitized, format, etc.), delegate points of contact between project and DSG (Jim / Coordinator on DSG end, Project contact determined by project), discuss next steps involved in Content Review for project and DSG, email summary of meeting. | ||
− | ==File Preparation== | + | ===File Preparation=== |
− | ''Lead by | + | ''Lead by Repository Manager in conjunction with Project, with delegation to others as needed'' |
* Metadata review and revision/creation | * Metadata review and revision/creation | ||
**Time intensive | **Time intensive | ||
Line 15: | Line 28: | ||
*Review of files for corruption, collection structure, etc. | *Review of files for corruption, collection structure, etc. | ||
− | ==Training and Instruction== | + | ===Content Review=== |
− | ''Lead by | + | ''Lead by Assistant Director and University Copyright officer'' |
+ | *Review copyright information | ||
+ | |||
+ | ===Training and Instruction=== | ||
+ | ''Lead by Coordinator, Assistant Directors, RAs'' | ||
*DRS Wordpress documentation for us | *DRS Wordpress documentation for us | ||
− | |||
*Future editing, adding, changes | *Future editing, adding, changes | ||
− | ==File Ingestion== | + | ===File Ingestion=== |
− | ''Lead by | + | ''Lead by Repository Manager and the Dev Team'' |
*Metadata into MODS/XML | *Metadata into MODS/XML | ||
− | *Fedora specific ingestion things | + | *Fedora specific ingestion things - formatting issues, etc |
− | + | ||
+ | ===WordPress Integration=== | ||
+ | ''Lead by Repository Manager, Assistant Director, COordinator, and Project'' | ||
+ | *Context Content Creation - static text for curation | ||
+ | |||
+ | ===WordPress / HTML Review=== | ||
+ | *Quality Assurance / Troubleshoots (Coordinator and RAs) | ||
+ | *DSG Review of Code (Dev Team) | ||
+ | |||
+ | ===Project Management=== | ||
+ | ''Lead by Coordinator'' | ||
+ | *Feature tracking (To find out what new features projects need and assure maintenance. Done in tandem with Eli and David) | ||
+ | *Quality assurance and troubleshooting (In tandem with David) | ||
+ | *Outreach and visibility | ||
+ | |||
+ | ==Toolkit Work and Tasks== | ||
+ | |||
+ | ===Development Work=== | ||
+ | ''Lead by Eli, David Cliff, and Dave Decamp'' | ||
+ | *Plugins to add functionalities | ||
+ | *Theming/customization for content presentation | ||
+ | |||
+ | ===Documentation=== | ||
+ | ''Lead by Julia, Sarah Sweeney, Amanda, Jim, and Abbie | ||
+ | *Metadata preparation guide | ||
+ | *Copyright "Hot Sheet" | ||
+ | *FAQs | ||
+ | |||
+ | ===Process Documentation=== | ||
+ | ''Lead by Ashley, Linda, Jim and Abbie'' | ||
+ | *Git code comments if necessary | ||
+ | *Project specific documentation goes in the associated wiki | ||
+ | *Essentially document all code development during this section | ||
− | == | + | ===Outreach/Visibility=== |
− | == | + | ''Lead by Jim and Abbie as part of project management'' |
− | * | + | |
− | * | + | ===Feature Tracking=== |
+ | ''Lead by Eli and David'' | ||
+ | *Maintenance | ||
+ | *Updates | ||
+ | *Second wave development | ||
==Documentation (Files and Links)== | ==Documentation (Files and Links)== | ||
+ | <!-- Things we will eventually link to once they're written | ||
+ | For users | ||
+ | |||
+ | DRS use upload guide | ||
+ | full DRS documentation | ||
+ | DRS toolkit guide | ||
+ | Copyright guide | ||
+ | outreach guide | ||
+ | Metadata prep guide | ||
+ | Basic wordpress guide | ||
+ | Github documentation | ||
+ | |||
+ | For us | ||
+ | TBS | ||
+ | --> | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | <!-- previously used list and info | ||
*Development Work: plugin, themes, customization. | *Development Work: plugin, themes, customization. | ||
Plugin: adds functionality (search, browse) | Plugin: adds functionality (search, browse) | ||
Line 45: | Line 118: | ||
*Training / Instruction of Project Team (Sarah, Jim) | *Training / Instruction of Project Team (Sarah, Jim) | ||
*File Ingestation (Sarah, Dev Team) | *File Ingestation (Sarah, Dev Team) | ||
− | *Contextual Content Creation: static text for curation (Project, Jim, Sarah, Amanda, Dave DeCamp) | + | *Contextual Content Creation: static text for curation (Project, Jim, Sarah, Amanda, Dave DeCamp) |
*DRS Content Integration (Project) | *DRS Content Integration (Project) | ||
*Quality Assurance (QA) and Troubleshooting (Project, Dave, and Jim) | *Quality Assurance (QA) and Troubleshooting (Project, Dave, and Jim) | ||
Line 52: | Line 125: | ||
*Outreach / Visibility (Jim, Amanda, Julia) | *Outreach / Visibility (Jim, Amanda, Julia) | ||
*Feature Tracking / Second Wave Development: maintenance, updates (Development Team) | *Feature Tracking / Second Wave Development: maintenance, updates (Development Team) | ||
− | *Project Management: onboarding and management (Jim) | + | *Project Management: onboarding and management (Jim) |
+ | |||
+ | --> |
Latest revision as of 09:40, 6 April 2017
Introduction
The CERES: Exhibit Toolkit is a WordPress plugin and theme developed by DSG staff. CERES is used to create websites that dynamically integrate images, text, video, and other digital materials into complex scholarly narratives and exhibits. Digital materials may be drawn from Northeastern’s Digital Repository Service (DRS) or the Digital Public Library of America, and potentially from other open repositories as well. Accepted projects will partner with the DSG and DRS teams to use CERES to securely store their project materials in the DRS and create a customized WordPress site to publish those materials on the web.
Project Work
Preliminary Meetings
- Attendees: Sarah, Amanda, Jim (DSG), project stakeholders, library liaison(s)
- Agenda: Introduce DRS to projects, get more information about project scope and intentions, discuss location of project data and state of data (digitized, not digitized, format, etc.), delegate points of contact between project and DSG (Jim / Coordinator on DSG end, Project contact determined by project), discuss next steps involved in Content Review for project and DSG, email summary of meeting.
File Preparation
Lead by Repository Manager in conjunction with Project, with delegation to others as needed
- Metadata review and revision/creation
- Time intensive
- Reposting
- Transference of files and other content
- Review of files for corruption, collection structure, etc.
Content Review
Lead by Assistant Director and University Copyright officer
- Review copyright information
Training and Instruction
Lead by Coordinator, Assistant Directors, RAs
- DRS Wordpress documentation for us
- Future editing, adding, changes
File Ingestion
Lead by Repository Manager and the Dev Team
- Metadata into MODS/XML
- Fedora specific ingestion things - formatting issues, etc
WordPress Integration
Lead by Repository Manager, Assistant Director, COordinator, and Project
- Context Content Creation - static text for curation
WordPress / HTML Review
- Quality Assurance / Troubleshoots (Coordinator and RAs)
- DSG Review of Code (Dev Team)
Project Management
Lead by Coordinator
- Feature tracking (To find out what new features projects need and assure maintenance. Done in tandem with Eli and David)
- Quality assurance and troubleshooting (In tandem with David)
- Outreach and visibility
Toolkit Work and Tasks
Development Work
Lead by Eli, David Cliff, and Dave Decamp
- Plugins to add functionalities
- Theming/customization for content presentation
Documentation
Lead by Julia, Sarah Sweeney, Amanda, Jim, and Abbie
- Metadata preparation guide
- Copyright "Hot Sheet"
- FAQs
Process Documentation
Lead by Ashley, Linda, Jim and Abbie
- Git code comments if necessary
- Project specific documentation goes in the associated wiki
- Essentially document all code development during this section
Outreach/Visibility
Lead by Jim and Abbie as part of project management
Feature Tracking
Lead by Eli and David
- Maintenance
- Updates
- Second wave development