Examples of workflows

From DLF Wiki
Revision as of 13:17, 12 May 2018 by Cristelags (talk | contribs)
Jump to navigation Jump to search

A workflow is a sequence of steps toward the completion of a defined task used to manage repetitive processes. Workflow modelling helps participants and stakeholders understand the sequence of steps and their roles in the process. It can also help identify patterns, gaps, and bottlenecks to enhance efficiency and improve team dynamics.

Please contribute examples of workflows to the DLF Project Managers Toolkit. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, any issues or solutions relating to the specific workflow.

The Library Workflow Exchange website: This site is designed to help librarians share workflows and best practices across institutions

Finding the Balance: a Discussion of 6 Digital Library Workflows (2016)

The following are from a panel at the Digital Library Federation Forum in 2016, "Finding the Balance: a Discussion of 6 Digital Library Workflows" which eventually became the article:

Finding the balance: Modelling successful workflows for digital library collections, Shaw, Emily Frieda; Garcia-Spitz, Cristela; Bragg, Molly; Hagedorn, Kat; Porter, Emily, Journal of Digital Media Management, Volume 6 / Number 3 / SPRING 2018, pp. 295-311.

Example 1. Key from the Digital Preservation Management (DPM) Tools workflow model from MIT Libraries (2013-2015)

Example 1. Key from the Digital Preservation Management (DPM) Tools workflow model from MIT Libraries (2013-2015). Specifying the conventions used in the workflow in a symbol key or legend assists with clarity and reusability in different versions or levels of detail of a workflow.


Example 2. High-level “lifecycle” model from The Ohio State University Libraries (2016) laying out the general steps in the workflow; it was developed as a tool for communicating with internal stakeholders who are not directly involved in reformatting collections, as well with peers and colleagues outside of the organization.

Example 3. More detailed view of the same “lifecycle” model from The Ohio State University Libraries (2016) adding the details of the subprocesses involved in each step; this model was created to help team members who are involved in the workflow understand all of the steps involved, in particular, curators, archivists and other collection managers who are interested in proposing a new reformatting project.

Example 4. Sketch of the ingest process from the UC San Diego Library (2016)

Example 4. Sketch of the ingest process from the UC San Diego Library (2016) created in order to brainstorm on the steps of the ingest process and demonstrate the difference in the workflow for simple “ongoing” smaller projects versus more complex and larger scale digital projects.

Example 5. An analysis of the Metadata Flow through different management systems from the UC San Diego Library (2012)

Example 5. An analysis of the Metadata Flow through different management systems from the UC San Diego Library (2012). Useful as both a thinking exercise and team building activity, this Prezi diagram presents extensive data flow models to determine the “database of record” or system(s) in which metadata was stored and managed. It also represents the relationships between the different data flow models, including inputs and outputs, and to create an image of the overall landscape.

Example 6. Cross-functional flowchart of the digital object lifecycle from UC San Diego Library (2010)

Example 6. Cross-functional flowchart of the digital object lifecycle from UC San Diego Library (2010) used to show the relationship between areas of the library from digitization to ingest into the digital repository. It was used to determine roles and responsibilities at each step, discuss the coordination and hand-off points, and work through issues, such as a what point and who should be doing quality control? After analyzing the workflow, one major outcomes was for project staff to consult with metadata specialists earlier in the process.

Example 7. “Deep Dive” Selection workflow: feasibility sub-process from Emory University (2015)

Example 7. “Deep Dive” Selection workflow: feasibility sub-process from Emory University (2015) depicts a specialized feasibility review conducted by staff in three distinct functional areas (digitization/reformatting, metadata, and copyright) which informs a larger project selection and prioritization process. While documenting this workflow, the specialists involved identified gaps and redundancies which led to overall process improvements around documentation and handoffs.

Example 8. A section from the Content Lifecycle Management workflow showing hands to indicate the handshake step when the custody of content transfers from MIT Libraries (2013-2015)

Example 8. A section from the Content Lifecycle Management workflow showing hands to indicate the handshake step when the custody of content transfers from MIT Libraries (2013-2015). The handshake step is explicitly noted to capture the moment that content changes hands and the responsibility for it moves from one group to another. It allows for roles to be defined and staff to be clear about the activities during the handshake. Using the handshake step in the digitization workflow at MIT has provided explicit chain of custody documentation, item tracking, and has ensured that content (physical or digital) is only transferred from one location to another by specifically designated persons at a scheduled date and time. This has also increased staff confidence using distributed digitization workflows knowing that explicit handoff and documentation is expected and can be traced.

Example 9. University of Michigan’s workflow between Digital Content & Collections and the Copyright Office (2016)

Example 9. University of Michigan’s workflow between Digital Content & Collections and the Copyright Office (2016) specifically detailing the roles of the agents between the divisions for creating rights investigation memos for each digital collection created and hosted. Because it identifies the role or skill set, and not the specific person, this workflow will not require constant updating when individuals change positions over time.

References

Allen MD, Chapman A, Blaustein B, Mak L. What do we do now? Workflows for an unpredictable world. Future Generation Computer Systems. 2015;42:1–10. Available from: [[1]].

BABOK: a guide to the Business Analysis Body of Knowledge. Toronto: International Institute of Business Analysis; 2015.

Epstein D, Maltzman R. Project workflow management: a business process approach. Plantation, FL: J. Ross Publishing; 2014.

Kmetz JL. Mapping workflows and managing knowledge. New York, NY: Business Expert Press; 2016.

Russell N, Aalst Wvan der, Hofstede AT. Workflow patterns: the definitive guide. Cambridge, MA: The MIT Press; 2016.
https://wiki.diglib.org/index.php?title=Examples_of_workflows&oldid=13562
wiki.diglib.org
CC-MAIN-2023-50
31669
application/http; msgtype=response
sha1:U3VHBNJN2FVZFETFQJJGCLFM4ML27OXF
<urn:uuid:db66d199-6849-4e78-a813-5b34c79dd873>
2023-11-29T08:26:02Z
69.164.214.222
text/html
sha1:2ICSUVPWPBNOBUGG7KGBVDFT2QUMC6ZG
<urn:uuid:20a5f0d3-ce11-4add-a811-79ab7afed0b2>
https://wiki.diglib.org/index.php?title=Examples_of_workflows&oldid=13562
response
<urn:uuid:8b9653ca-76c2-4769-807f-c42710271941>
isPartOf: CC-MAIN-2023-50
publisher: Common Crawl
description: Wide crawl of the web for November/December 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-117
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/