The web-based hosted book maintenance tool allows authorized personnel to perform the functions necessary to maintain all aspects of the book series environment.  The publisher must first designate a book coordinator (or coordinators) to maintain the book series and then supply the following basic information about the book coordinator to AMS in order to create an account with username/password access to the books maintenance tool.

The following book maintenance functions are available:

Maintain Book Coordinator Information

The book coordinator can modify their maintenance account information once the account is established. The account is initially seeded with their email address as the username and password. Book coordinators are encouraged to initially change their password and at least once per year thereafter.  Confirmation email is sent to the book coordinator when maintenance account information is updated.


Upload Home Page Content

Each book series home page has a content region that contains publisher-supplied information about the book series. This content is updated and inserted into the home page when the home-content.html file is uploaded by the book coordinator via the web maintenance tool. File naming requirements apply.  Validation checks are performed and the home page content is placed in a "pending" area for preview once uploaded. Confirmation email is sent to the book coordinator. After previewing, the "pending" content can be posted to the public site via the web maintenance tool.


Each hosted book series is comprised of at least 2, and at most 4, types of HTML pages, all of which are based on a strict template that contains identical branding imagery and global navigation links.

The last two pages listed below are relevant only for book series which post individual articles or chapters separately from full book volumes.

HTML Page Type Page Description Created by:
Common to all book series
Book Series Home Book series-specific home page Content supplied by the publisher via the home-content.html file
All Volumes listing List of all volumes of the book series with links to either the TOC pages (if individual articles are posted) or the book volume files (if no individual articles are posted) Automatically generated based on the current set of volumes posted
Relevant to book series which post individual articles
Volume TOC Volume Table of Contents Automatically generated when a book volume is uploaded or posted
Article Abstract Abstract of article Automatically generated when a volume is uploaded or posted

Upload Image Files

The book coordinator can upload image (jpg, gif, png) files associated with the book series environment. Validation checks are performed and images are immediately made available to the public once uploaded.  Confirmation email is sent to the book coordinator.


The base HTML template contains 4 image regions, which allows for some degree of customization for the book series. Images have strict size and naming requirements. All images here are provided by the publisher.

Image Region Image Description Image Name Image Size WxH
Publisher Publisher branding (logo) publisher.(jpg, gif, png) 120x80
Home Page Imagery on Home Page only home-page.(jpg, gif, png) 120x175
Book Series Name Book Series name branding, logo (optionally used instead of text for series name) bookseries-name.(jpg, gif, png) 480x80
Navigation Imagery optionally located under global navigation region (perhaps the book cover). navigation (jpg, gif, png) 110X112

 

Upload Support Files

The book coordinator can upload a (.tar, .zip, .gzip) file which contains one or more predefined PDF book series support file(s).  File naming requirements apply.  Validation checks are performed and the file(s) are immediately made available to the public once uploaded. Confirmation email is sent to the book coordinator.


The base HTML template contains a consistent set of global navigation links mapped to a defined set of book series support pages. Book series support pages are in PDF format and have strict naming for portability and maintainability. All book series support pages are provided by the publisher in PDF format.

Any particular book series may choose, when setting up the book series with AMS staff, to exclude any particular support files from the book series environment.

Global Navigation Link Page Description File Name File Format
Overview Book Series Overview overview.pdf PDF
Authors Author Information author.pdf PDF
Editorial Editorial Board Information editorial.pdf PDF
Contact Contact Information contact.pdf PDF
Subscribe Subscription information subscribe.pdf PDF

Upload Volume Files

The book coordinator can upload a (.tar, .zip, .gzip) file containing files for each volume.  Each volume must have at least 2 files (.xml and .pdf) associated with it, as described in the Book Volume File Naming table below. File naming requirements apply.  Upon successful upload of the volume files, validation checks are performed.  If the files pass the validation tests, they are posted for public viewing.  Confirmation email is sent to the book coordinator.


 

Book Volume File Naming (for upload)
In the following examples, "prefix" represents the abbreviation for the book series followed by the number of the volume. Example valid prefix values could be:
abcd34 efgh12.1 xyz42a
prefix.xml XML file conforming to the ams_hostedbook1.dtd document type
prefix.pdf PDF file of the full volume
Optional files
prefix-toc.pdf PDF of the table of contents of the volume
prefix-frontmatter.pdf PDF of the frontmatter of the volume


Upload Subscriber Access Files

This feature is available only for those book series which have arranged with the AMS for subscriber access authentication.

The book coordinator can upload a (.tar, .zip, .gzip) file which contains IP and/or username/password access related files.  Updated access is activated immediately.  File naming requirements apply.  Confirmation email is sent to the book coordinator.


Access to the book series is granted via IP or username/password. It is the obligation of the publisher to supply IP and/or username/password information in the proper format. The IP access file should be a list of class B IP addresses (one entry per line) that identify only valid subscribers. The IP’s can be listed as individual addresses or an address range using a wildcard. The IP access file must conform to a strict naming convention for each book series. The IP access file name prefix should be the book series code assigned to the book series followed by the .ip extension (e.g. abc.ip); all in lowercase.

 

Example of IP Address Access File (abc.ip)
130.44.* Allow access for all IP’s in this range denoted with a wildcard (*).
~130.44.1.* Disallow access for all IP’s in this range denoted with a preceding tilde (~).
~130.44.2.27 Disallow access for a specific IP denoted with a preceding tilde (~).
125.111.12.1 Allow access for this specific IP address

 

The username/password file should contain the username/password pairs (separated by a space - one entry per line) for each valid subscriber. Usernames and passwords should be comprised of only alphabetic and numeric characters and be no more than 15 characters each in length. The username/password file must conform to a strict naming convention for each book series. The username/password file name prefix should be the book series code assigned to the book series followed by the .pw extension (e.g. abc.pw); all in lowercase.

Example of Username/Password Access File (abc.pw)
smith1 gooduser Allow access for user who enters a username of “smith1” and password of “gooduser”.
jones8 davey Allow access for user who enters a username of “jones8” and password “davey”.

 


Subscriber Access File Naming (for upload)
jrnlcode.ip IP based subscriber access file
jrnlcode.pw Username/password based subscriber access file
whatever.tar or whatever.zip or whatever.gzip Bundled subscriber access files.

Technical Support

Subscription and overall book maintenance is the responsibility of the publisher. Book series support pages (particularly contact.pdf) should refer users directly to the publisher for support. AMS will not handle support inquiries directly from subscribers. Technical support inquiries will only be handled if they originate from the publisher.