Manchester University Press Visit Agenda

Journals on the Web

The initial objective is to put one issue of each journal (6) on the Web in Adobe Acrobat format(.pdf).
  1. General Questions
    • How is a consistent approach to be achieved initially and over time?
    • What responsibility for maintenance do MUP want?
    • How much training do they need?
    • Do they wish to purchase both Adobe and the programme
    • Will all issues be held at one time or just current issues? We are expecting 16 issues a year.
    • Will they wish to upload past issues?
    • How many files in one issue (8)?
  2. Convert postscript files to .pdf,
    • What disk space do they fill?
    • How will they be delivered to us?
    • Can they be delivered on a CD-ROM?
    • What naming convention to be used?
    • What order will files be in?
  3. Front end design
    • Are they happy with existing style or do they want redesign?
    • Are there additional 'Corporate Identity' logos or stylings which they have on paper or digital?
  4. Database
    • Can we have a contact for technical liason?
    • What is the current data design - documents or URLs required.
    • What details are needed for logging in?
    • Do they want us to supply a separate database?
    • How are we to interact with existing DB?
    • What data needs to be shared?
    • Which database is currently being used?
    • Who is maintaining database of subscribers?
  5. Site Security
    • How will the site be updated? (us by FTP?)
    • Will we do it or will MUP?
    • If we do it we need to have password to site
    • Are they happy to give us the site password?
  6. Search engine
    • Is it search across multiple journals and/or issues?
    • What are the typical queries?
    • Will a fielded search be required? (if so there will be a need for a database).
  7. Alerting by e-mail for new issues
    • Subscribers email address required
    • Alert me flag in subscription database
    • Subscribers username and password required
    • Subscribers query (if required).
  8. Live Site
    • Will the system be stand alone or have to share data, such as subscribers, with other systems?
    • NT or UNIX?
    • IIS or Apache?
  9. Timeframe
    • 20 working days to beta then 5 to final upload from acceptance of quote
    • thereafter 3 days for new issues from delivery of files
    • aim for upload end September

Document Dated: Tue Aug 4 17:00:48 1998
Modify this document
Previous Version