University Library Scholarly Publishing Office, Unit Goals, FY 2000-01

The Scholarly Publishing Office is a new organization within the University Library, charged with developing tools and methods for the electronic publication and distribution of scholarly content. The SPO intends to support the traditional constructs of journal and monographic publication in an online environment, as well as to publish scholarly work expressly designed for electronic delivery. The SPO will also monitor campus concerns and questions around electronic publication and dissemination of scholarship, and work to address those concerns both through appropriate venues for discussion and in building its services. The services of SPO will be made available to the University of Michigan community as part of the Library's service to the University. Over time the SPO will extend its services beyond the campus as part of consortial efforts, strategic partnerships, or as contract services.

In its first year, SPO has a number of goals to establish its services and its presence on campus. It will undertake an environmental study to understand the campus needs for electronic publishing services and the obstacles to widespread adoption of electronic publishing mechanisms by campus authors and editors. Simultaneously, it will work on developing the services and systems for managing and delivering electronic content. These will include a management system that enables management and delivery of electronic journal articles, design of a tool to support peer review over the Web, methods for managing an electronic subscriber list and specification of statistics that can be gathered about use of the online publications.

In addition, the SPO will assume responsibility for managing the Library's role in the ACLS History E-book Project. The Library, through DLPS, has an existing commitment to the American Council of Learned Societies to provide technical development and support for its E-book project. This five year project is intended "to assist scholars in the electronic publishing of monographs in history, to help assure the continued viability of the history monograph in today's changing publishing environment, and to explore the intellectual possibilities of new technologies." Moving this project into the SPO will provide an ideal opportunity for developing mechanisms for delivering electronic monographs, mechanisms that can then be generalized to other kinds of monographic content.

1 Program building

1.1 Build understanding of the needs and concerns of campus publishers by conducting an environmental study, including

Compile list of scholarly publishers on Campus (including content, frequency of publication, etc.)
Contact editors- introduce ourselves, get information from editors on their current tools, processes, their interests in e-publishing, their needs in this area, their concerns -- perhaps a formal survey?
Analysis and summary of survey information

	Timeline:	October-March
	Responsibility:	Rosenblum with assistance of hourly worker, and input from Bonn

1.2 Work with OVPR/Rackham to promote moving subsidized journals to electronic publication

	Timeline:	Ongoing
	Responsibility:	Bonn

1.3 Possible meeting of university libraries engaged in publishing efforts in their first two years of operation with no more than 5 FTE to talk about sharing tools, information, purpose.

	Timeline:	To be determined. Possible first meeting at midwinter ALA.
	Responsibility:	Bonn

1.4 Bring in or visit with staff of Highwire and Project Muse in order to learn from their experience and understand their aims.

	Timeline:	To be determined. Possibly in conjunction with All things Digital. Aim for a speaker by March.
	Responsibility:	Bonn

1.5 Communicate with and educate library staff about purpose of SPO and its services

develop website (in tandem with development of DLI site)
brochure and paper information (December)
hold information meetings with library staff (reference staff, collection development staff, PR dept, Health Services, Media Union esp librarians or departments who might have more contact with faculty.) February-March

	Timeline:	Ongoing with milestones as noted
	Responsibility:	All staff, coordinated by Bonn

1.6 Analysis and education of staff about issues like copyright, authentication & access, and other issues that editors are likely to ask about (as determined though conversations and environmental study)

	Timeline:	Ongoing
	Responsibility:	All staff, coordinated by Bonn

2 Content building

2.1 Communicate with and educate faculty, particularly faculty editors, about purpose of SPO and its services.

announce our services
set up meetings with editors
create demonstration, showing examples of current publications (MQR, Phil Imp, TMR) and services
set up mailing list for editors to announce new services or make general announcements
develop training materials on using software needed/stylesheets, etc.

	Timeline:	Ongoing
	Responsibility:	Rosenblum, Bonn

2.2 Support for the Philosopher's Imprint

2.2.1 Create Web environment , searchable text and desired display

Get feedback on Word Style Sheets
Finalize Quark.dtd
Build mapping script to transform content to textclass.dtd
Transform Dear Self to textclass.dtd
Develop web template

	Timeline:	by end of November
	Responsibility:	Rosenblum, Programmer

2.2.2 Provide continuing data transformation support

Copy editing: formatting/checking layout of text in Word template
Data transformation
Template management
Get feedback on and modify if necessary templates and quark.dtd as necessary

	Timeline:	Ongoing
	Responsibility:	Rosenblum, Interface Specialist, Programmer as needed

2.3 Support for The Medieval Review

Move TMR from mail robot submission to journal management system
Facilitate moving TMR to text class to resolve outstanding issues about URLs and tag set.

	Timeline:	by end of November
	Responsibility:	Rosenblum

2.4 Support for the Michigan Quarterly Review

2.4.1 Develop online system for current publication

Train staff on SPO tools and methods necessary for online publication
Explore methods for digitizing artwork
Establish relationship with Sans Serif to minimize duplicative effort
Develop web environment

	Timeline:	September-February, first issue online June
	Responsibility:	Rosenblum, Interface Specialist

2.4.2 Digitize backfile

Obtain and convert available electronic files and implement in online system (October-December)
Locate funding for conversion of print files (November-December)
Plan and schedule imaging and OCR of backfile

	Timeline:	Milestones as noted. Backfile conversion complete by end of year.
	Responsibility:	Conversion of existing electronic files coordinated by Rosenblum, other conversion activities coordinated by Bonn.

2.5 Work on publication opportunities with Slavic Department

2.5.1 Digitize and put Cross Currents online.

Resolve copyright issues (October-November)
Digitize and OCR page images (December-February)
Additional indexing and encoding (March-April)
Online implementation (May)

	Timeline:	October-May with milestones as noted
	Responsibility:	Rosenblum coordinates, Interface Specialist

2.5.2 Explore online publication of other publications of the Slavic Department.

	Timeline:	Ongoing
	Responsibility:	Rosenblum

2.6 Support for 4DP2

Assist in completion and submission of proposal to CoE. Work on data transformations and system building as directions and content emerges.

	Timeline:	Dependent on Media Union staff and CoE
	Responsibility:	Bonn for proposal, others to be determined as project takes shape.

2.7 Provide support for electronic publication of dissertations as program develops as needs and directions develop.

	Timeline:	Ongoing, depending on directions determined by Rackham and the Library.
	Responsibility:	Dependent on types of tasks to be determined

2.8 Work with Library staff to identify publication possibilities within their collections.

	Timeline:	Ongoing
	Responsibility:	Bonn

3 Retrieval System

3.1 Assess needs for modification of textclass retrieval system for journals

	Timeline:	Ongoing with initial analysis and specification in December
	Responsibility:	Interface Specialist, Programmer

3.2 Apply textclass retrieval system to ACLS monographs when they appear

	Timeline:	Dependent on ACLS timelines
	Responsibility:	All staff as appropriate, working with DLPS

3.2.1 Explore and implement XML style sheets/style associated display. Demo with IE5.

	Timeline:	Education and training September-December, implementation dependent on arrival of content, availability of browsers with xml support
	Responsibility:	Rosenblum, Interface Specialist

3.3 Develop generic, customizable interface/search and display templates

4 Management system and tools

4.1 Develop basic management tool for collection of bibliographic data and submission of completed files.

	Timeline:	July for specification, August for implementation
	Responsibility:	DLPD staff with CS

4.2 Modify journal management system to support issues-based publishing (currently supports only article-based publishing)

	Timeline:	Specifications in February, implementation dependent on programmer hire
	Responsibility:	Interface specialist, Programmer

4.3 Specify system to support peer review process

	Timeline:	Specifications March-April, implementation dependent on programmer hire,
	Responsibility:	Interface specialist, with input from Rosenblum, Bonn, Programmer

5 Electronic subscription management

5.1 Assess authentication user management system as tool to manage permissions for journal subscribers. Share with editors to garner feedback. Pass feedback on to DLPS staff.

	Timeline:	Internal assessment, November. Work with editors, February and on.
	Responsibility:	Rosenblum, Bonn

5.2 Assess possibilities for charging mechanisms for ACLS and other content

	Timeline:	Initial assessment January then ongoing depending on ACLS timelines
	Responsibility:	Programmer with CS, Interface Specialist, Bonn with contributions from ACLS project staff

6 Continue exploratory work on print on demand

6.1 Establish relationship with vendor to produce books from existing digital files (i.e. MoA books).

	Timeline:	by end of December
	Responsibility:	Bonn assisting Preservation staff as needed.

6.2 Establish method for selectors to request print replacements

	Timeline:	January, dependent on Preservation staff
	Responsibility:	Bonn assisting Preservation staff as needed.

6.3 Establish method for individuals to request print replacements for library

	Timeline:	February-March, dependent on Preservation staff
	Responsibility:	Bonn assisting Preservation staff as needed.

6.4 Establish methods for individuals to be able to purchase print replacements

	Timeline:	February-March, dependent on Preservation staff
	Responsibility:	Bonn assisting Preservation staff as needed.

6.5 Move responsibility for reprints to Preservation Dept.

	Timeline:	by end of year
	Responsibility:	Bonn assisting Preservation staff as needed.

6.6 Explore issues of branding and marketing reprints.

	Timeline:	ongoing
	Responsibility:	Bonn

6.7 Explore need and venues for print services in relation to content published through Library.

	Timeline:	ongoing
	Responsibility:	Bonn

7 Support for ACLS

7.1 Specify usage statistics required by ACLS and other publishers.

	Timeline:	Initial assessment March then ongoing depending on ACLS timelines
	Responsibility:	Rosenblum, Bonn, with contributions from ACLS project staff

7.2 Adapt existing stat mechanisms to meet publisher needs.

	Timeline:	Initial April-May then ongoing depending on ACLS timelines
	Responsibility:	Programmer with CS/HZ, Interface Specialist, Bonn with contributions from ACLS project staff

7.3 Design ACLS interface

	Timeline:	Dependent on ACLS timelines
	Responsibility:	Interface Specialist, Bonn with contributions from ACLS project staff

7.4 Evaluation of ACLS XML

	Timeline:	Dependent on ACLS timelines
	Responsibility:	Rosenblum

7.5 Liaison to DLPS digitization/backfile conversion services

	Timeline:	Dependent on ACLS timelines, probably starting December
	Responsibility:	Bonn

8 Transitional goals

8.1 Release Directory of Ethnic Organizations

	Timeline:	ASAP depending on approval from O. Feinstein
	Responsibility:	Bonn, Sheppard

8.2 Release Annotated Bibliography of the French Revolution

	Timeline:	Dependent on approval from Skib/Amman
	Responsibility:	Sheppard

8.3 Complete and release BMP Index

	Timeline:	by January
	Responsibility:	Rosenblum

8.4 Release the Index to the Transcripts of the French Political Trials.

	Timeline:	ASAP depending on approval from Herrada
	Responsibility:	Sheppard

8.5 Finish MoA4

Continue management of project until texts are online
Analyze cost data and prepare handbook
Prepare final report

	Timeline:	by January 31
	Responsibility:	Bonn

8.6 Continue as liaison to DLPS for Arts of Citizenship, Making of Ann Arbor and the Saline Historical Photographs project.

	Timeline:	ongoing
	Responsibility:	Bonn, Sheppard