Project Plan 4: Projected Timeline & Workplan

Please note draft status: feedback welcome as comments – final version liable to change

Overall Timeline of Workpackages:

2010 Feb March April May June July
WP1 |–> –> –> –> –> –||*
WP2 |–> –> –>* –||
WP3 |–> –>* –> –> –> –||*
WP4 |–> –> –> –> –||*
WP5 |–> |–> |–> –||

“*”=tangible product delivered.

Workpackage 1: Oversight of signposting landscape study and technical exemplars

Responsible: Project Manager


● Oversight of budget, timelines and deliverables from the other team members and their workpackages.

● Liaison with JISC Executive on the presentation and overall delivery of this work to the sector based on an agile and adaptive approach (as things will change that this plan will not encompass!).

● Liaison with JISC Collections on their work in eBook usage and OAOPEN eBook business models.

● Final structure of signpost (aka table of contents) to all of the outputs from the various workpackages, including tangible products (e.g. reports, prototypes) and intangible products (discussions, skills learned) and other exemplars that arise outside of the project and in the community that are related and worth noting.


● Project Posts (short paragraph style updates) on the progress of the project (weekly?). These posts should be used to collect the intangible products (discussion, skills, etc) that the various team members are producing as part of their workpackages, as well as the changes that occur to the plan of the project as it progresses.

● Final website and sign-post (table of contents) of all the deliverables from all the workpackages in the project.


Workpackage 2: Technical Landscape Exemplars and Recommendations

Responsible: Open Authoring and Publishing Technical Expert


● Research into current overall technical landscape of digital monograph publishing in Higher Education and Further Education in both the UK and internationally.

● Collection of technical exemplar use cases of digital monograph publishing both in the Academic Sector and Other sectors (commercial, business, government, military, etc).


● A technical landscape paper on digital monographs outlining both exemplar use cases from around the world and recommendations for how JISC could influence the technical landscape so as to support UK HE/FE authors in publishing more of their content as digital monographs.

● Versions of the landscape paper in both HTML (for the website) and as an ePub for distribution via email to digital mobile devices.

● Liaison with the project manager to assure deliverable is meeting overall context of work the project is attempting to achieve.

Previous examples of landscaping papers and guidance websites can be found here**:

Linkeddata landscape horizon scan

Persistent Identifiers Landscape study



Workpackage 3: Technical prototype and exemplar for author wordprocessing environment

Responsible: Technical wordprocessing and authoring tool expert.


● Prototype development of technical protoype for authoring digital monograph in a traditional wordprocessing environment (Word)

● Prototype development of a technical prototype for authoring digital monographs in a non-traditional wordprocessing environment, e.g. Blogs or GoogleDocs

● Liaison with the independent Author perspective expert for the purposes of allowing commentary and guidance.

● Liaison with the project manager to assure deliverable are meeting the overall context the project is attempting to achieve.


● Prototype 1 exemplar of traditional wordprocessing environment (Microsoft and Open Office Word)

● Prototype 2 exemplar of non-traditional wordprocessing environment (blogs, googleDocs)

● Liaise with UK Author User


Workpackage 4: Independent commentary by an Active author on the technical implications that the project discovers.

Responsible: Independent authoring user perspective


● Liaise with Project Manager (WP1) re overall

● Liaise with Landscape Exemplars and comment upon them and the implications for authors

● Liaise with Technical prototype (WP3) and comment upon their findings and implications for authors

● Liaise with device technical specification expert and


● Active participation and communication with the other workpackages and their decision making process per end user perspective.

● Blog posts commenting on each of the workpackages outputs and their findings and outputs.

● Blog posts commenting on various author perspectives / demographics (e.g. first time doctoral dissertation theses authors, retired academic authors, etc.)


Workpackage 5: Update of reader device types on wikipedia pages including specifications and references to project findings.

Responsible: Device Technical Specifications Expert


● Investigation into the various device types including specifications and applicability of use to digital monographs.

● Liaise with wikipedia editor on acceptable process for updating wikipedia pages to assure longevity of reference and specification formats.

● Liaise with the project manager re overall aim of project and what references should be made to project outputs and finding within Wikipedia articles.


● Updating of wikipedia pages with specifications and applicability, specifications and usability of devices for academic digital monographs.

● References within wikipedia pages pointing back to the outputs of the project

● List of updated Wikipedia pages for use and reference by the project.

Posted in project plan | Tagged , , , | Comments Off on Project Plan 4: Projected Timeline & Workplan

Project Plan 3: Project team relationships

Please note draft status: feedback welcome as comments – final  version liable to change

Team Roles:

Project Manager

Responsible for co-ordination of the project team and oversight of budget. Will ensure delivery of project outputs within agreed timescales.

Technical Publishing Expert

Responsible for digital monographs state of the art study and synthesis of project outcomes to produce technical landscape paper

Technical Wordprocessing Tool Expert

Responsible for developing prototype tools for authoring digital monographs in traditional and non-traditional environments.

Author User Perspective Expert(s)

Will provide independant expert commentary on digital monograph adoption within chosen academic spheres.

Device (reader/tablet/mobile) Reader Expert

Will be responsible for investigating current device types, ebook specifications and aggregation routes.

Posted in project plan | Tagged , , | Comments Off on Project Plan 3: Project team relationships

Project Plan 2: Aims, Objectives and Final Outputs of the project

Please note draft status: feedback welcome as comments – final  version liable to change

Aim: To provide guidance on the current technical landscape that will enable individual author(s) to envision and publish their monograph to multiple “eBook” devices with the simple single click of a button.


● To provide guidance and a signpost to the sector on how the usability, business models and technical implications of digital monographs relate to one another (WP1)

● To provide a technical landscape paper with exemplar case studies on how JISC can best technically support the University sector in supporting Academic authors to publish their manuscripts formatted for digital devices (WP2)

● To provide a technical demonstrator for how authors can utilise their wordprocessing environments to visualise and publish their digital monographs online and to multiple devices (WP3)

● To provide an author viewpoint of how authorship should potentially change given these new devices and how readers will encounter their overall reading experience on these devices (WP4)


Each workpackage will deliver a tangible product (as well as commentary on the intangible products) produced during the course of the project, these products include:

● A webpage that will provide a single signpost (table of contents) to the various landscape exemplars, guidance and technical exemplars produced as part of the project that will be oriented towards a stakeholder audiences within the UK HE & FE sector.

● A Landscape study including exemplar case studies and recommendation for how the sector could enhance the technical ability to publish digital monographs to a multitude of devices.

● Two technical exemplars demonstrating how both traditional wordprocessing tools (e.g. Microsoft Word) and nontraditional wordprocessing tools (e.g. Blogs or GoogleDocs) could be technically enhance to enable ease in one click digital monograph publishing.

● A blog of reflections by an author on the above outputs and products and how they are applicable to various authoring groups (subjects areas) and demographics (new academic, retired academics, etc).

● A series of Wikipedia pages updated on the technical specifications of various digital devices and how they can be used for digital monographs, along with footnotes and references to the products produced from the project.

Posted in project plan | Tagged , , , | Comments Off on Project Plan 2: Aims, Objectives and Final Outputs of the project

Project Plan 1: Benefits and context

Please note draft status: feedback welcome as comments – final version liable to change

User Problem

Readership of web content is moving to other devices beyond the typical “at desk” or “on laptop” screen. Mobiles (Android, iPhone, etc.), Tablets (iPad, iTab, etc), eReaders (eInk, Pearl, etc.) and other “eBook” style devices are increasingly becoming a welcome alternatives for reading. Accordingly, books produced by Academic authors need to be enabled in terms of formatting, process, aggregation and delivery of monographs to these new devices. Perhaps most significantly, the technical barriers of publishing to this multitude of devices needs to be lowered, if not removed all together so as to assure that any individual author can “technically” publish their content with the single click of a button[1].

Accordingly the problem that needs to be “solved” is two fold: a.) Academic authors must be able to author in their native wordprocessing environments with support within those environments for how the content can best be visualised and delivered to multiple devices, and b.) readership of monographs should be able to consume content via the device of their choosing and with features to their liking. This project will primarily focus on the former with an eye to the latter, but with a clear remit to the individual author working within an Academic setting producing scholarly monographs for this new breed of device.


JISC has actively recognised that one of the key value propositions of the Web is its “openness”. It has supported several open movement such as open access, open education resources, open scholarship and so forth and so on. It is currently in the process of formulating an ‘Open Agenda’ which will align the various open movements and their value for UK Higher and Further Education. This technical work should begin to establish how open access monographs can fit within the overall ecosystem of scholarly communication.

JISC has also also previously invested in the business and usability considerations of eBooks (via the National JISC eBooks Project), and so any technical work going forward will need to liaise with this overall national usability study. In addition, further work has been funded via the OAOPEN effort at JISC collections, whereby the business models for publishing will be investigated. Again the technical considerations will need to be compared and contrasted with how they affect the business models. Further touch-points between these efforts are built into the below workpackages.

[1]This technical work is intended to be a simplification of the publishing process. We fully recognise that the processes required to publish a widely read book are much more complex than a “single click”. None the less, leveraging the Web Architecture means that the technical process of authoring, formatting and publishing a monograph on the Web should be no more difficult than a single click, ipso facto this is a technical pilot to demonstrate that the web is still a *simple* tool that any individual can utilise to publish to any number of web enabled devices. It is also important to note that this work in not attempting to compete with publishers as we feel this activity will in fact help support publishers in having the most open and interoperable format by which to edit, format and deliver content themselves to a wider audience. We also fully recognise that publishers provide a value-added service that enhances content; where we are only suggesting that the technical aspects of one-click publishing is for the value in technically demonstrating that anyone can format and make their content deliverable to a multitude of eBook devices (reader/tablet/mobile/etc).

Posted in project plan | Tagged , | Comments Off on Project Plan 1: Benefits and context