Difference between revisions of "DSG DRS Pilot Project Workflow"
Jump to navigation
Jump to search
Line 23: | Line 23: | ||
===Training and Instruction=== | ===Training and Instruction=== | ||
''Lead by Sarah, Amanda, and the coordinator (Abbie or Jim)'' | ''Lead by Sarah, Amanda, and the coordinator (Abbie or Jim)'' | ||
− | *DRS Wordpress documentation for us | + | *DRS Wordpress documentation for us |
− | |||
*Future editing, adding, changes | *Future editing, adding, changes | ||
Line 30: | Line 29: | ||
''Lead by Sarah Sweeney and the Dev Team (Eli and David)'' | ''Lead by Sarah Sweeney and the Dev Team (Eli and David)'' | ||
*Metadata into MODS/XML | *Metadata into MODS/XML | ||
− | *Fedora specific ingestion things | + | *Fedora specific ingestion things - formatting issues, etc |
− | |||
===WordPress Integration=== | ===WordPress Integration=== | ||
+ | ''Lead by Sarah Sweeney, Amanda, Jim, David Decamp, Project, and Abbie'' | ||
+ | *Context Content Creation - static text for curation | ||
===WordPress / HTML Review=== | ===WordPress / HTML Review=== | ||
Line 60: | Line 60: | ||
===Process Documentation=== | ===Process Documentation=== | ||
''Lead by Ashley, Linda, Jim and Abbie'' | ''Lead by Ashley, Linda, Jim and Abbie'' | ||
− | *Git code comments | + | *Git code comments if necessary |
− | + | *Project specific documentation goes in the associated wiki | |
− | *Project specific documentation | + | *Essentially document all code development during this section |
− | |||
===Outreach/Visibility=== | ===Outreach/Visibility=== | ||
Line 87: | Line 86: | ||
*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) |
Revision as of 13:15, 14 July 2015
Introduction
-content outlined in DRS Project Toolkit CFP
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 Sarah Sweeney 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 Amanda and Hillary
- Review copyright information
Training and Instruction
Lead by Sarah, Amanda, and the coordinator (Abbie or Jim)
- DRS Wordpress documentation for us
- Future editing, adding, changes
File Ingestion
Lead by Sarah Sweeney and the Dev Team (Eli and David)
- Metadata into MODS/XML
- Fedora specific ingestion things - formatting issues, etc
WordPress Integration
Lead by Sarah Sweeney, Amanda, Jim, David Decamp, Project, and Abbie
- Context Content Creation - static text for curation
WordPress / HTML Review
- Quality Assurance / Troubleshoots (David and Abbie)
- DSG Review of Code (Eli and David)
Project Management
Lead by Jim and Abbie
- 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)
- Development Work: plugin, themes, customization.
Plugin: adds functionality (search, browse) Theme: how the content (facets, display settings, context) is presented Time Frame: Early July
- File Preparation: materials, metadata, file support (Sarah and Project)
- Content Review: copyright issues (Project, Hillary, and Amanda)
- Documentation (Jim, Julia, Sarah, Amanda)
- Training / Instruction of Project Team (Sarah, Jim)
- File Ingestation (Sarah, Dev Team)
- Contextual Content Creation: static text for curation (Project, Jim, Sarah, Amanda, Dave DeCamp)
- DRS Content Integration (Project)
- Quality Assurance (QA) and Troubleshooting (Project, Dave, and Jim)
- DSG Review of Code (Development Team)
- Process Documentation (Jim, Ashley, and Linda) — DSG doc, e.g. DRS Tookkit, on our wiki; projects’ processes on their GitHub repository wiki (if they have a GitHub repository)
- Outreach / Visibility (Jim, Amanda, Julia)
- Feature Tracking / Second Wave Development: maintenance, updates (Development Team)
- Project Management: onboarding and management (Jim)