getting to digital publishing at wvu
TRANSCRIPT
Getting to Digital Publishing at WVUDr. Cheryl E. Ball | @s2ceball
Thank you.3 parts: Kairos, Vega, DPI (10 min each)
Getting KairoticPart one: The Story of a Journal
Text
Part One
(Digital) Publishing Studiesrhetoric/compositiontechnical/professional writingcommunication design(electronic literature)
courtesy of Maia C, Flickr CC license
Job title: Publishing studies (traces my own academic and editorial history) is about theorizing practice and focusing on production in an apprenticeship model with students. Heavily dosed with information literacy, info architectures in the creation of digital texts while also focusing on readers needs through specific genres that editors help create.
Digital = media-rich, open-access, design in relation to born-digital work, information architecture, etc.
Digital Scholarly GenresToolsArchivesKnowledgehttp://www.hastac.org
- distinguishing DP from DH - within and outside of DH- DH: collaborative, professionalizing, open > all things C&W has done for a lot longer. (I dont call myself a DH person unless I need funding)(for me, longer history of C&Wand all its names, e.g., digital writing studies).naming the kinds of knowledge production in digital writing
Hypertexts/HypermediaNew media scholarshipDigital scholarshipOnline scholarshipWebtextsScholarly multimediaDesigned researchOn naming, see Ball, 2004; Lauer 2009, 2012
Naming
http://kairos.technorhetoric.net
Text
Kairos > publishes research about rhetoric, technology, and writing pedagogy. Just published its 20th anniv issue.
Kairos: started in 1996editor since 2001- premier digital journal in writing studies (15% acceptance rate)- OA (libre), independent, peer-reviewed- webtexts
http://kairos.technorhetoric.net/13.2/topoi/delagrange/index.html
Principal of webtext deisgn: UNIQUE DESIGNS, where form::content meet.
A major goal of webtexts is to enact their rhetorical arguments through design work. (This is a piece from 2009, argument about juxtaposition and wunderkammers facilitating invention)
Webtext principal: Process-based researchIn the August 2014 issue of Kairos, interaction design researchers Einar Sneve Martinussen, Jrn Knutsen, and Timo Arnall (2014) published a peer-reviewed webtext that showcases the design-process methodologies they used to construct a project called Satellite Lamps.
As Martinussen (2013) explained, the team explored and visualized howGPS takes place in urban environments. The team has looked at therelationships between urban space, time and satellite-geometry, anddesign and has developed instruments and techniques for visualising the presence and the fluctuations of satellite signals.
Satellite Lamps
http://kairos.technorhetoric.net/19.1/inventio/martinussen-et-al
The opening video shows how the teams time-lapse film methodology works to visualise these signals. The three authors worked together to produce the video, as well as curate multiple slideshows from their photographic archive, research additional scholarly materials for the rich transdisciplinary literature review, write the linguistic (written) content, and design the webtext in Ruby (which they had to transfer to HTML for Kaiross archival purposes).
Kairos isnt the only one, BUT is the OLDEST & longest-running.Handmade vs. CMS
> Ive studied technical sustainability and longevity of these journals, most of which dont gave a great track record.
See Eyman & Ball 2014a, 2014binfrastructures for webtext publishingsocialscholarlytechnical Photos by miuenski on Flickr
SCHOLARLY: the importance of design as a rhetorical vehicle for scholarly argumentation; SOCIAL: the available means of assessment and peer-review within a collaborative, open setting; and TECHNICAL: questions of sustainability of the scholarly work, regardless of form, in the rapidly evolving technological ecosystems of the Internet.
(These infrastructures overlap. All of these infra. come together in Kairos.)
Open Journal Systems OJS is installed locally and locally controlled. Editors configure requirements, sections, review process, etc. Online submission and management of all content. Subscription module with delayed open access options. Comprehensive indexing of content part of global system. Reading Tools for content, based on field and editors choice. Email notification and commenting ability for readers. Complete context-sensitive online Help support.https://pkp.sfu.ca/ojs/
OJS provides technical infrastructure, What OJS is [editorial workflow]HOWEVER [problems w/OJS]
problems with OJSlook/designrigid workflowsno mm capabilities
peer-review processtier 1: staff reviewtier 2: open board reviewtier 3: 1-1 mentoringPhotos from Knight Foundation, Aaron Hockley, & Deb Nystrom: Flickr
At Kairos, we embrace design as part of the invention process through our mentorship of authors in pre-submission collaborations and through our collaborative peer review process
1996 peer-review via YahooGroups
The problem with reviewing webtexts in this manner via email is the problem of translating nondiscursive elements such as page layout or the photos of the authors daughter into a linear set of words.
In addition, the reviews are asynchronous, which creates gaps of time sometimes weeks between responses. While that aids in thoughtful participation by the board, it doesnt facilitate the kind of immediacy in peer-response that digital media texts sometimes require.
design editingaccessibilityusabilitysustainabilityrhetoricityhttp://kairos.technorhetoric.net/styleguide.htmlSee Ball, 2013; Ball & Eyman, 2015
During the peer-review process, we developmentally edit for rhetoricity. After a piece is accepted for publication, we edit their designs (including the code, as needed) for sustainability, accessibility, and usability. All of these are rhetorical concerns: an author who chooses to design her piece in Adobe Flash chooses a limited set of sustainable, accessible, usable, and readable features that may change over time, or even disappear (see Sorapure). These design choices function as part of a webtexts scholarly and technical infrastructures as well as part of the social infrastructure of Kaiross collaborative authorial and editorial workflows.
What and how we edit for design depends entirely on the text in front of us at any given moment.
Are there transcripts?Are the filenames properly named and formatted?Do the links work?Do the images have alt txt?Are the media files uploaded to the correct server location & contain appropriate metadata?
[WVU Summer Seminar - Melanie Schlosser, accessibility focus. This summer, its on sustainability of ETDs as a scholarly genre.] Sustainability is a whole nothr talk when it comes to Kairos. We have been working to sustain our scholarship for 20+ years, and part of how we get there is to take close care of each and every webtext.
Once accepted, a submission runs through our production process.
Kairos copy-editing rotations
LOTS of staff. Here: sample copy-editing rotation
Manual version control
So how do we manage?
Getting systemsPart Two: The Story of the Vega Archipelago
Text
All this leads me back to a lack of technical infrastructure that can handle these types of processes for innovative and multimedia journals
> 15 years working towards CMS, not right funding
Oslo School of Architecture & Design (AHO)
> Vega. [Fulbright in 2013-14; Mellon grant]
Andrew MorrisonOslo School of Architecture and Design, Norway
Text
AndrewFulbright
Benglerdesign-development studio in Oslo, Norway
Text
developers- publishing CMS expertisescience publishing expertise> Vega [name of platform, Norway, archipelago, Cairrrrn]
Vega. sense of location
islands/tide
rising from the rubble of boring scholarly publishing
modularity for venues, FREE, multimedia, data sets,
editorial workflows
On my trips to Oslo
polished editorial workflows, with Simen
based in large part on research 602 students helped conduct in Spring 2015> publishing practices of editors and authors. several articles in the works
Vega: Tracks, Issues, Activities
jump out to PDF
Vega FeaturesAuthor toolsmultimedia authoring, LaTeX conversion, collaborative writingEditor toolsopenclosed review,authoreditor review,version control & DAMVenue toolsmodular workflows,OA or embargoed,rich metadatacross-refs & retraction featureshttp://tinyurl.com/ball-vega
GO SHOW SOME
Vega stack
Behind the scenes.
Asset store, like Github, is fast and co-located for quick delivery. Vega should control its own asset servers (so in case the API doesnt change). Plug-ins (that others make) work as bridges between Vega and Kora or Hydra.
Q: We need more specific use cases. How do you see asset systems relevant to Vega. Copying/downloading images from repo for asset store for quick delivery (but copyright). PLUG-IN: for Hydra repo to retain control of content so it delivers to Vega a reference (linked image) but keeps original/rights. > What IS PUBLISHED?: But when it is deep archived, everything needs to be saved in one place. Is the metadata enough?? Does the media artifact need to be there??
(CAVS ACT) MIT is using SANITY (CMS) as an asset store/IR. Its a lower level than what Sanity (a toolkit, ready by Summer) can do. Vega would be a second system potentially that could share.
Getting sustainablePart Three: The Story of the DPI
Text
While Vega is a collab project with Norwegians, it will eventually live at WVU, in WVU Libraries, specifically under banner of Digital Publishing Institute.
Arrived at WVU and almost immediately met Jon Cawthorne, Dean of WVU Libraries, who shared my vision of digital scholarship. Official as of January 2016.
whiteboard drawing (still in FLUX) after a DTF meeting (Disappearing Task Force on WVU Librarys Digital Presence in the 21st Century
Digital Publishing Institute
3 branches of DPI: DH center if it werent just H.
Research in the DPIsupport for digital research projects (e.g., tools like Vega, archives/collections)research related to publishingon- and off-campus partnershipsun/funded partnerships
- reaching out to faculty
DPI Outreach/Servicejournal hostingdata management helpcopyright helpservice publishing for university/community
Pedagogy and the DPIclasses related to DPI mission internships; workers for research projectsaffiliated facultyworkshops for internal/external constituents
Proposed Digital Hub of WVU Libraries
Reframe how digital content is handled at ALL levels of the library. Cant just be DPI. Cant just be scholarly comm librarian. e.g., OA copyright question? subject librarian is at forefront. sends to scholcomm person, who runs workshops with DPI & subject librarian help.e.g., new OA initiative in Press? combines forces with WV Regional History Center or special collections and DPIs pedagogical initiatives to create service publishing opps that promote campus and scholarly missions.
Our initial challenges: workflows (DPLAfest, but Kairos). Staffing, which we are currently being creative with. Our goal is to be at capacity, producing up to 10 digital projects a year, JUST out of DPI, plus workshops and affiliated classes within 5 years.
timeline = Encourage use cases THIS summer. release in Fall 2017/Spring 2018
c. Inge Ove Tysnesthank you
http://ceball.comhttp://vegapub.comhttp://kairos.technorhetoric.nethttp://dpi.lib.wvu.edu