Web Content Management System

tiredbeginnerInternet and Web Development

Dec 8, 2013 (3 years and 8 months ago)

72 views



-

Questionnaire


1



Marin County Free Library






Web Content Management System

Jadu Incorporated Detailed Questionnaire Response





Web Content Management

System (WCMS)

Questionnaire
2010





-

Questionnaire


2




1. Detailed Specifications and Vendor Response



Questions

Vendor response

MUS
T HAVE ITEMS


The CMS product selected will need to support
multiple administrators with their own login
accounts.


Each content administrator and/or webmaster receives their own logon credentials with
customized access privileges.

The CMS must have the

ability to produce, receive
and integrate into the existing website RSS feeds


RSS is standard within the system.
Jadu's
RSS and ATOM feed manager enables
external content import so that content from external sources can
be configured for
consumption an
d display within relevant areas of the website
.



Jadu CMS automatically publishes news and event information as RSS feeds, allowing
website visitors

to subscribe to content.


As well as RSS feeds, the
Jadu
CMS also includes a comprehensive API (called
My
Jadu API) which provides a RESTful interface
allowing enabling you to allow Library

content and data to be re
-
used on other systems. This feature forms an integral part of
Jadu‟s „Open Data‟ initiative


which Tim Berners
-
Lee
is also sponsoring and promoti
ng
.


Provide Web 2.0 services integrations for popular
sites, such as Twitter, Flickr, Facebook, Delicious,
RSS, Dopplr and other social networking sites. This is
needed as we continue to incorporate more
interactive features into the website.


Jadu is b
ased on open standards and easily integrates with other third party systems

such as Web2.0 and social media services
. Jadu
currently has a fully integrated Twitter
client and an integrated Facebook application will be out in our next release. All other
Soc
ial Media applications using APIs are easily integrated into the Jadu CMS



-

Questionnaire


3



ADA reader compatible pages are needed to better
support our visually impaired patrons.


Jadu develops all its products to comply wit
h Web Content Accessibility G
uidelines.
Speci
fically for front
-
end websites, Jadu templates are created to be accessib
le and
adhere to web standards.


We author CSS to strict standards and have a policy for avoiding the use of both CSS
hacks and Javascript to enable site functionality.


We work hard
to ensure that all templates conform to a minimum of AA and as much of
AAA as possible (that do not require manual checks). All pages generated in the CMS
are designed to be Valid XHTML.


Jadu websites also include

„site settings‟,
which enables website vi
sitors to select
accessibility settings to enhance their browsing experience (e.g. text only, change font
size, color, character spacing, etc.).


Compatibility with different browsers to view our
website(s), or simply referred to as browser
-
agnostic, is r
equired. Such browsers currently
include, but are not limited to: Internet Explorer
(Versions 6, 7 & 8), Mozilla Firefox, Apple Safari and
Google Chrome.


Jadu CMS is entirely browser based, cross browser compatible and requires no plugins
or applets. Jad
u undertakes browser compatibility testing as when new browser
versions are released.


Remote users can easily access the CMS to perform updates out of business hours and
regardless of geographical location.


Jadu CMS supports Internet Explorer

v6, v7, v8
, Firefox,
Safari, Chrome,
Mozilla on
Windows, Linux and Mac OS
.
Jadu do
es

not generally test on Internet Explorer 5 for
Mac as it is not supported by Microsoft.


Adobe Flash Player must be supported, as we do
produce Flash files.



The Jadu CMS supports

the uploading and embedding within pages of SWF files as
standard. In fact the CMS includes a dedicated Multimedia Manager which provides
management of images, video, audio, podcasting and video
-
casting as well as image
and multimedia galleries. Any items

uploaded to the Multimedia Library can be
embedded within content via a simple non
-
technical interface.


Video formats are automatically converted to SWF on file upload to the Multimedia
library enabling playback in any browser with the common Flash playe
r plugin.




-

Questionnaire


4


Mobile devices such as iPods, iPhones, Droids and
Blackberry devices need to be supported.



All content is separated from layout using CSS.
As such, t
he Jadu CMS
renders
content
in many ways including for mobile / handheld devices using multip
le presentation layers.
All Jadu CMS template sets (including the out of the box Vanilla template) come with a
mobile / handheld CSS. The development of additional device specific stylesheets could
be undertaken by Jadu as a professional service.


The CMS

permissions must allow site administrators
full access, and make it possible to set permissions
for other groups or individuals.


Authoring rules can be created on a per user basis, with the facility to specify the
different areas that content contributo
rs can access within the CMS and the associated
permissions for each user in relation to accessing those areas. In addition, it is possible
to specify areas of the Document Editor a user can access, allowing even text
formatting options

(such as the italic
s button, underline, bold…etc)

to be configured on a
per user basis.


There needs to be a reliable statistics gathering
mechanism that gives at least the same reporting
capabilities of Google Analytics, but does not have to
use Google Analytics.


Jadu CM
S has its own analytics tool provided as standard.

Jadu Statistics‟ is a web
based site analytics system that looks at all user activity on your website.


Featuring public overview of statistics and uptime, it also supplements this with a much
more powerf
ul and extensive reporting facility for retrieving usage reports over different
periods of time, for particular documents, or for all usage within a particular navigation
category.


Jadu Statistics can also email scheduled PDF or HTML reports generated fro
m custom
templates on a scheduled basis.


Jadu Statistics provides you with instant visual reporting on what your visitors are
looking at and how they are interacting with your website.




-

Questionnaire


5




In addition to Jadu Statistics all Jadu CMS websites have the faci
lity to use third party
Javascript based analytics solutions such as Google Analytics. The CMS features a
dedicated non
-
technical interface to apply the appropriate code to facilitate this.


The reports generated by Google Analytics complement those availa
ble through Jadu
Statistics to give you a full picture of all of your website activity.


In relation to search activity analysis,
Jadu is a Google Enterprise Professional Partner
and deploys Google search with the majority of its implementations through th
e Google
Mini or Google Search Appliance. The administrative interfaces for both types of Google
search hardware include search reporting facilities.


The Google Search administrative interface provides the facility to generate reports for


-

Questionnaire


6


search queries f
or a specified timeframe. Report types can be configured to include
searches that returned results as well as searches returning no results. It is possible to
specify certain terms to be excluded from the search reports as well as specify the
number of top

queries and keywords to show.


In addition, it is possible to generate search logs that list all search queries for a
specified timeframe in a format similar to common log format (CLF). Such logs can be
stored in or added to external applications allowing

deep analysis and historical trending
if required.



-

Questionnaire


7



Google search report interface


Google Analytics also provides search specific information, including search terms, total
unique searches, page views for search results, exits after search queries, numb
er of
query refinements, time spent on site after search and search depth.




-

Questionnaire


8



In our current system, it is difficult to update and
locate content. Updates to existing content need to
be quick and easy to accomplish.


With Jadu‟s easy to use interface it
is very easy to locate and update content. As an
added benefit, after a document has been saved, the

preview
screen
displays the
content within a realistic context (i.e. using the website design templates) and gives
editors the ability to edit
and save
co
ntent in
-
line.

This saves time as the user does not
have to flip back and forth from Preview to the WYSIWYG to make content
modifications


all can be done within the preview mode.



Content preview with in
-
line editing facility.



Authorized staff must

be able to easily add, edit and
delete content to specific sections of the website for
which they have permission to do so.


Authoring rules can be created on a per user basis, with the facility to specify the
different areas that content contributors ca
n access within the CMS and the associated
permissions for each user in relation to accessing those areas

such as add, edit and
delete
.




-

Questionnaire


9



Staff must have the ability to easily upload images,
.pdfs, and other files to be hosted on the server
through the
admin tool.


Users can easily upload images to appear next to content as specified by
predetermined Templates. Additionally, images can be uploaded, optimized, resized
and easily placed within the content using the WYSIWYG editor.


Documents, such as P
DFs, can be attached to any webpage as supplemental items.

There must be an ability to seamlessly integrate with
County of Marin calendaring system. The
calendaring system of choice is Trumba, which uses
JavaScript and AJAX. More information on Trumba
c
an be found at http://www.trumba.com.



For a full and seamless integration, a

Jadu

Homepages


widget could be developed to
present the Trumba calendar to website users on any Jadu
web
pages that this widget
was added to, removing the need for the standard

built
-
in

Jadu Events feature and
subsequent calendar widget.


A custom script would be required to then present the list of events within the context of
the main websites design, as is done on the following example page:
http://www.marinlibrary.org/news
-
and
-
events/calendar
-
of
-
events/?trumbaEmbed=date%3D20100928



This
will

result in a seamless integration of your Trumba solution to your
Jadu
-
powered

website.


All content produced must be auto
-
formatted to
comply with agreed upon CSS. The CSS should allow
for an overall look and feel to be maintained
throughout the website, but also allow for each part
of the website to have its own CSS for a differe
nt
appearance if desired. An example would be The
CRM page, which has a very different look from the
rest of our existing website. Please note the current
CRM page does not currently reflect how we would
like it to appear or function. There are 4 separate
documents enclosed pertaining to the design of the
CRM web pages. The documents may also be
downloading using the following links:

http://marinlibrary.org/rfp/crm
-
website
-
redesign
-
doc.pdf

http://marinlibrary.org/rfp/crm
-
website
-
Your
have full control over
your

CSS and can manually create, edit and upload style
sheets as required.


CSS can be authored and edited

in all leading WYSIWYG editing tools, such as
Dreamweaver and GoLive. These CSS templates can be copied, edited and uploaded
to the Jadu Intranet as new templates.


The Jadu Stylesheets en
gine allows for the re
-
design/
re
-
branding of specific areas of
cont
ent through CSS that can be uploaded through the Jadu Stylesheet manager.
Access to this part of the system can be granted on a per
-
user basis.


For even more individualistic styling, Jadu Galaxies can be used.
The Jadu CMS
Galaxies feature enables the ra
pid delivery of discrete CMS powered websites in
minutes using the t
emplate selector.
Custom templates can be designed and created
and then uploaded to the system for corporately styled and branded

templates.
Additional templates can be added to the Galaxi
es template library.




-

Questionnaire


10


flowchart.pdf

http://mari
nlibrary.org/rfp/crm
-
website
-
redesign
-
home
-
page.jpg

http://marinlibrary.org/rfp/crm
-
website
-
redesign
-
secondary
-
page.jpg


Jadu Galaxies template selector


Prior to activating, or publishing, any content, auto
-
verification of links needs to occur for that content.


Links should be checked by the content author and again by the content approver
before
going live. This may be done via the dedicated Link Map available for each item
of content. This clearly lists all pages that the item links to (both internal and external
links) and provides users with the ability to test each link prior to publication.


The Jadu CMS Link Map also provides users with the ability to check whether any other
pages within the website are linking to their content prior to deletion/removal.


The Jadu CMS will automatically remove any dynamically generated links to content
that i
s deleted or moved within the underlying navigation taxonomy.


To ensure your links are always valid, Jadu CMS features a dedicated link checker. This
can be scheduled to run on a regular basis with the resulting report being emailed to a
specified user in

order to take any necessary action.




-

Questionnaire


11


Authorized staff should be able to add this content
without having to go through layers of
security/approval for content that they are allowed
to edit/publish.


It is your decision how many layers you wish to have in

your approval workflow. Jadu
operates with a minimum of two. In this way, content creation and publishing are
separated. More layers of approval and workflow routing, including collaborative
workflow may be added at your discretion.

Content updates sh
ould automatically populate
relevant sections throughout the site without the
need to edit each of the web pages where that
content should appear.


The Jadu CMS processes all content as raw XHTML stored in the database. Web
delivery is performed dynamical
ly and cached to optimize performance.

This means
that data can be published once and will update across the website wherever it is
located.


Content can
even

be shared across instances of other Jadu CMS driven websites using
drag and drop, and other syst
ems using the Jadu MyAPI feature.


Error checking needs to be performed prior to
publishing, or otherwise activating, a web page. The
error messages need to be understandable and
specific for a largely non
-
technical based audience,
so that it’s clear what

needs to be corrected.


When saving content prior to activation the Jadu CMS automatically checks whether all
mandatory fields have been completed to determine whether the item is ready for
publication. Any fields that are incomplete and require attentio
n are highlighted
so

the
user can clearly identify the actions that they are required to take before the page is
activated.




-

Questionnaire


12




Errors are clearly highlighted for non
-
technical users




-

Questionnaire


13



Web pages produced must be compliant with
standards listed at http://
www.w3.org and must
pass validation testing using
http://validator.w3.org/.


All Jadu websites are designed to support the World Wide Web Consortium (W3C)
accessibility standards and actively promote the adoption of the W3C's Web Content
Accessibility Gui
delines (WCAG), including manual accessibility audits of templates to
confirm compliance.


Code quality and semantic markup are key to providing an accessible and usable
website. To this end, all Jadu websites are developed using CSS and built with valid
XHTML.


The Jadu Document Editor, the core of our web content management software, outputs
only valid XHTML markup to ensure that all pages of your site validate to the W3C's
XHTML standards.


Should the site fail W3C validation when tested
,
Jadu will ame
nd the templates as
required.


Jadu recently negotiated a partner pricing partnership with AbilityNet, one of the World's
most respected independent
testing and
accessibility experts.


As a result, AbilityNet can offer independent essential „express‟ UAT r
eviews and tests
of Jadu customer websites as part of the Jadu CMS implementation, at a significantly
reduced rate.


The ability to have links, and authentication for
remote databases like OverDrive, Safari books,
LearningExpressLibrary.com, etc. is neede
d. Other
databases that we currently link to can be found at
http://www.marinlibrary.org/digital
-
content/index.php. Tracking of use of these
databases is also required, or at least tracking of
how often the links are being selected.



The current Marin lib
rary solution appears to link to a separate script which logs a link
being followed for reporting purposes, and then redirects the user on to the target
system where they can then authenticate themselves directly upon this system.


Creation of links within

Jadu to these external databases is a simple content task. Built
into the core features is a statistics area where the webservers access logs are
analy
z
ed to provide details of the number of visits a URL has received. All that would be
required via custom

develop
ment would be a custom script
on the Marin Library system
that would receive the hit when a user clicks a link, and takes the appropriate action to
then header redirect the user to the target system, thus creating a visit on the Marin
system that c
an be reported upon before the user leaves the system. This would require
some custom

development.




-

Questionnaire


14


There must be a method to archive, or make
inactive, content and make it unavailable from
general access via the Internet. The following must
occur:


Cont
ent can be taken “offline” manually or through scheduling.
,
Jadu CMS includes a
content scheduling interface, enabling Administrators to specify when content needs to
go live, or be removed from the live site i.e. for a set period of time, with a particu
lar
action to occur when this period ends. An example might be that the document
becomes archived after it has been live for the period of one week from today.


When content is scheduled Administrators can set an automatic email alert to remind
them when t
he scheduled date is reached.



Jadu Content Schedule interface




Saving of inactive pages must occur, and the
ability for staff to search both active and
inactive content is needed. The public must
only have the ability to search just the active
content.



Inactive pages are saved. The content author and anyone having more powerful rights
to view/edit that content can search for it and locate it easily. The public will not be able
to search for or see this content.



Archived, or inactive content, must h
ave an
edit option so archived information can be
updated and saved as new content or
republished as an updated version of the
original content


Any content which is inactive can be edited by the proper authorized users and
republished either on demand or

scheduled to go live at a predetermined date and time.




-

Questionnaire


15




Staff should be able to access archived
content, but it must be clear that the
content has been archived so they know
what they are viewing is currently inactive.
The system must support our staff w
ith easy
to understand and use features for quickly
adding, updating, and publishing content in
a browser
-
agnostic interface.


The

content will be clearly marked so the user knows that the content is not live in the
system.


The Jadu CMS has been purpos
ely built to enable the devolvement of site management
throughout
higher education institutions
, with the emphasis on ease of use for non
-
technical departmental content editors.

The WYSIWYG Document Editor enables non
-
technical content contributors to ente
r
content in a simple, word processing environment.

No HTML skills are required. Copy and paste text direct from documents, add links,
change text formatting, add images (including alt tags)
-

everything that you would need
to do to publish content creati
vely and accurately.

The Document Editor allows the true separation of content from layou
t, while

maintaining W3C standards compliant XHTML code output.

CSS can be configured to
match formatting styles for consistent presentation and rendering across an en
tire
website.

The Document Editor also allows for multiple undo and redo, cut and paste, text
alignment, bulleted and numbered lists, links, special characters and a Microsoft®
Word™ HTML code cleaner
-

to strip out any non
-
compliant code generated by such

proprietary applications.

The Document Editor also supports the creation of tables. Functions include the ability
to add, insert, delete rows and columns, split / merge cells, change rows / columns
sizes, border styles before and after table is inserted i
nto the page, without editing the
HTML. These tables are marked
-
up with the appropriate table headers/titles to ensure
accessibility compliance.




-

Questionnaire


16



The Jadu CMS document editor


A flexible WYSIWYG tool to setup templates for
pages with click and drag capa
bilities is needed. The
tool should allow for copying and pasting from other
sources such as Dreamweaver, or even simply
notepad.


The Jadu Stylesheets en
gine allows for the re
-
design/
re
-
branding of specific areas of
content through CSS that can be upload
ed through the Jadu Stylesheet manager.
Access to this part of the system can be granted on a per
-
user basis.


CSS can be authored and edited in all leading WYSIWYG editing tools, such as
Dreamweaver and GoLive. These CSS templates can be copied, edited an
d uploaded
to the Jadu Intranet as new templates.

Notepad and other lesser editors are supported
as well.




-

Questionnaire


17



Good Search Engine Optimization is needed to help
rank our web pages higher in all of the major the
search engines like Google, Yahoo and Bing.


The Jadu CMS is proven in generating
very

accessible and search engine
optimized

websites. Aside from the highly semantic code, Jadu CMS implementation also include
s

a number of key

out of the box


features and implementation tasks that make
the
Jadu
CMS

website highly
search engine optimized
:


The Jadu CMS produces standards
-
compliant XHTML code, which is a
key component
to

a search engine friendly site. In most instances metadata fields are pre
-
filled
. W
here
this is not possible
,

it is mandatory that t
he CMS user provides data for any missing
fields.


Additionally, Jadu provides a sitemap.xml file, which some search engines (e.g. Google)
will use to crawl your site. This ensures that all required pages are indexed.


As standard
,

all Jadu sites feature:




Mandatory non
-
technical keyword/metadata management.



Mandatory non
-
technical addition of keywords and alt tags for images.



Editable page names.



Page summary text.



Use of text instead of graphics for page titles.



Non
-
technical management of friendly URLs.



Ability to easily link to external sites from content, along with dedicated links
database.


Use of metadata tags is required.


All pieces of content require metadata (tags/description) as part of the core Jadu CMS.



-

Questionnaire


18



Training from the vendor is very im
portant and must
be included. Training of all of our staff that will use
some or all of the CMS features either by vendor or
our own staff as a “train the trainer” scenario must
occur.


Jadu provides a full service solution including design, implementatio
n, project
management, training, hosting and consultancy.

Jadu
has traine
d
individual
s in every
institution where
the CMS has been deployed. As a
result
, we

have attained significant
experience with delivering engaging, high quality and informed training

sessions. We
provide training aimed at both system administrators and content authors, and have
well
-
established training plans for both roles.


As well as detailed training focused on the use of the Jadu CMS, as standard our
training incorporates modules

on effectively managing and enhancing content and
writing for the web. We can provide train
-
the
-
trainer based sessions to enable
customers to devolve their Jadu CMS further following implementation
-

an approach
that has been successful with a large numbe
r of our clients.


All training material is provided for the customer to use including session outlines,
manuals and presentations.


We offer a range of Jadu Learning courses focused on enabling you to make the most
of your Jadu CMS implementation in terms

of management and additional development.


Lastly,
Jadu provides an online support facility where customers can download
information, including training manuals for the CMS.


There must be security precautions such as editing
locks in order to prevent mu
ltiple editors from
modifying the same document at the same time.


Jadu provides content locking as a configurable option in Workflow. The CMS is flexible
in that Administrators can decide which users have content locks and which do not.

Additionally, Jad
u keeps an archived version of the content every time it is saved. This
way, if another author makes changes that must be undone, you can easily roll back to
a prior version with a click. You can also put two versions side by side to see what
changes wer
e made.


A knowledge base or FAQ type of system needs to
be implemented for both Internet access by all and a
separate system for Intranet access for staff only.


There is a fully featured online support and knowledgebase website at
support.jadu.co.uk, w
hich is only available to
all Jadu
customers.

Jadu
also
use
s

a
support/incident help desk system to facilitate efficient technical support. All queries are
logged and recorded and assigned a unique reference number.



-

Questionnaire


19



Spell checking is a highly desired
feature to help
reduce the amount of errors when creating content.


The Jadu CMS features a spellchecker as standard along with a readability checker that
analy
z
es how easy a piece of content is to read online based on the content‟s
grammatical structure
using the Gunning Fox Index
(
http://en.wikipedia.org/wiki/Gunning
-
Fog_Index
). This index is used to ensure that your
content is easily readable by the largest segment of the population by providi
ng you with
a readability score and average reading age.

This is a particularly nice feature to have
as a public Library system to ensure ease of access to information for all persons.


The spellchecker is complemented by a dictionary enabling certain wor
d/terms (e.g.
place names) to be added and ignored during future checks.


As part of the copy and paste feature, allowing
Microsoft Word formatted content to be pasted into
the text area, and correcting the formatting
automatically would be quite helpful.

Stripping out
the additional overhead added in the coding
produced by Microsoft Word would also be
necessary.


The Jadu CMS document editor allows content to be copied and pasted into the CMS
from external applications such as Microsoft Word.

Jadu automa
tically strips out non
-
valid markup generated from proprietary applications
(
such as MS Word
)

and replaces
this with valid XHTML as standard.




Having the ability to automatically resize images to a
suitable size for display would save a considerable
am
ount of time. The resizing must also optimize the
size of the file for faster web page loading.


The Jadu CMS includes an image editor as standard. An image file size limit can be
configured as part of the CMS implementation. In addition, the image uploa
d facility
includes an option to optimize an image/file size for the web upon upload.



-

Questionnaire


20



SHOULD

HAVE ITEMS


The Administrative module should be designed to
accommodate at least 32 simultaneous active users
that are working with content.


Jadu CMS is a sc
alable system designed for high demand websites.


There are no known client issues regarding scalability in terms of content volume,
publishing processes, domains and concurrent user sessions.


Jadu has designed its infrastructure for subst
antial scalabili
ty within
singl
e server,
separate web server/
database, clustered and load balanced environments
, with
significant capacity to allow for growth on our manage
d systems.


In the event of significant growth, additional servers can be added to a cluster to
incr
ease capacity.


(
There are no additional licensing charges for hosting CMS on multiple application
servers or clustered / mirrored database servers.)


Printable page options should be easy to setup
where applicable.


All Jadu sites include print.css by d
efault. Presentation is switched dynamically for all
media
-

i.e. printing from a Jadu site generates a formatted document according to
paper size.


Web pages should have expiration date & time, or a
“Never Expire” option so that pages that should be
remo
ved after a certain date & time will
automatically be archived.


Jadu CMS includes a content scheduling interface, enabling Administrators to specify
when content
(such as web pages) will

go live, or be removed
/archived

from the live
si
te. For example, a

document becomes archived after it has been live for the period of
one week from today.


When content is scheduled Administrators can set an automatic email alert to remind
them when the scheduled date is reached.




-

Questionnaire


21



Jadu Content Schedule interface


Web
pages should have an option to be made
available immediately, as a default, or an option to
schedule them to appear on a user specified date &
time.


(this is the same answer as the one above… it was pasted in case this document is
dissected during review
)


Jadu CMS includes a content scheduling interface, enabling Administrators to specify
when content
(such as web pages) will

go live, or be removed
/archived

from the live
si
te.







-

Questionnaire


22



Currently, larger changes or additions to the site are
too complex to

be made by library staff and require
contracting of web developers and additional
payment to Hannon Hill for integration into the site.
Ideally it should be possible to make reasonable
changes and additions to the site in the future
without having to incu
r additional costs.


Jadu CMS is extremely user friendly and empowering for non
-
technical users. Creating
an editing Homepages, Webpages and Document pages requires no technical skill and
can be performed by library staff.


Jadu Homepages are widget ba
sed so library staff can simply drag the widgets into the
homepage editor, complete some configurations, drag the widgets to where they would
like them to display and save/submit the page.

Experience in working with digital archives is highly
desired as o
ur CRM has an ever growing collection of
digitally archived information.



Jadu ha
s

integrated with various CRM applications via a number of different
methodologies. We have also dealt with exposing large volumes of internally stored
historical data / docu
ments from separate DMS solutions.


The Jadu CMS allows for full XML integration with back office systems, and provides a
full
y documented

developer API for those wishing to do any additional custom
developments in
-
house.


Jadu has its own simple, advanced

and
customized

methods of joining up systems with
Jadu or the front end website.


• Simple integration: Taking data from a back office database and importing it into a
searchable Jadu database with a
customized

web template. This kind of functionality
req
uires only basic development knowledge; Linking to web based systems e.g. SX3.


• Advanced Integration: Using automated data extracts to transfer data to the web
database; integrating with payment providers using supplied APIs; integrating with other
Local

Authority Software products e.g. GIS using supplied APIs.



Custom

Integration: System level integration with back office systems
,

such as CRM
,

to enable two
-
way information flow. Jadu primarily writes WebService (using SOAP) or
remote procedure calls (
RPC) or leverage existing supplier WebService APIs.


The 'MyJadu API' also empowers the users of your web site to create applications and
'mash
-
ups' around your content by
utilizing

the Jadu web based (REST), public
development framework.




-

Questionnaire


23


Using an API key

issued through the Jadu Control Centre, your users can become an
extension of your development team.


The Jadu Homepages feature provides another excellent framework for providing
integrations between sites, systems and applications via embeddable widgets
.


Experience in working with CONTENTdm is
recommended. CONTENTdm is used for managing
the digital archived data for the CRM. More
information about CONTENTdm can be found at
http://www.contentdm.org
.



A scoping
exercise would be required to understand your requirem
ents for how you
wish to expose

digital collections within your website, and how best we can go about
integrating the two systems into a seamless and user friendly experience.


CONTENTdm is an OCLC prod
uct. OCLC is located less than 1
5

miles from the Jadu,
Inc. Headquarters in Columbus Ohio. Jadu has personal connections with some of the
team at OCLC should integrations be required.


A large user support community for the CMS
package is desired.


Jad
u holds an annual customer conference
. R
egional user groups and customers
collaborate

&
share knowledge and code via Jadu's online support portal
.

The ability to easily integrate third
-
party scripts,
templates, applications, etc. is desired.


Jadu‟s o
pen data architecture makes it highly compatible. Jadu‟s code snippet tool
allows users to insert javascript code via the WYSIWYG editor with ease. It is common
practice for third parties to develop templates for use in the Jadu CMS.


3
rd
party vendors
that can support the CMS package
is desired.


Jadu provide
s

direct support for the CMS package rather than
utilizing

3
rd

party
vendors, and we have a reputat
ion among

our customers for delivering unprecedented
levels of support for our systems.


Jadu use
s

a support/incident help desk system to facilitate efficient technical support.
All queries are logged and recorded and assigned a unique reference number.


Support.jadu enables users to submit and track support queries online


with full real
time reporti
ng and audit. Tickets can also be commented on and closed by the
customer.


Social media linking and sharing and being able to
populate content to
-
and
-
from Facebook, Twitter,
Flickr, etc. from
-
and
-
to our website is requested.


Jadu comes standard with a
fully integrated Twitter client which is subject to Jadu
workflow. A Facebook module is in development and will be available in a point
release. Integration with other social media applications (such as Flickr) can be easily
accomplished through the APIs
.




-

Questionnaire


24


Provide a way to more easily produce web content
in multiple languages. We currently produce both
English and Spanish versions of most of our content.


If perfect translation is not required, Jadu uses Google Translator which is good enough
to communi
cate the intent of text for understandability.


If perfect translation is required, a human must perform the translation and populate the
webpage. Jadu‟s Galaxies functionality (smaller CMS‟s spawned from the core CMS)
are a good tool to use as branding c
an be replicated to the CMS Galaxy but the content
can be fully translated into the non
-
English language.


The ability to have Unicode characters available in
our content would be helpful.


Jadu CMS fully supports Unicode and can publish in multiple lang
uages, including
roman and non
-
roman alphabets (provided the correct browser language packs are
installed on the client machine).



Jadu CMS enables one version of a document to be published in English, and another
i
n an alternative language, e.g.

Arabic

o
r Hindi
.



Jadu multi
-
language support


Jadu's WCAG compliant web pages enable audio playback via screen readers such as
Browsealoud.



-

Questionnaire


25



A simple process to highlight certain items would be
helpful. Examples include new book lists, book
reviews, hot topics

and new information in general.


Jadu‟s widget functionality allows users to dynamically pull in widgets to webpages that
highlight certain key information such as news…etc. In addition, simple text widgets can
be used to highlight more static content su
ch as book lists, book reviews…etc.

Provide an option for patrons to submit book
reviews which should have the options of:


1.

Allow reviews to be approved by staff and
then be viewable by anyone on the Internet


2.

Automatically be viewable by anyone on the
Internet without needing approval


The difference between #1 and #2 in this question seems to hinge on approval. In #1
you are looking for some approval workflow, in #2 you are asking that reviews go live
without review/approval. Both of these options a
re easily accomplished with Jadu. We
will instead focus
our

answer on the tougher aspect of this functionality which is how
you allow
your
users to enter data
(book titles, authors, ISBN…

and their review) into
the system and how that data is processed.


Option #1: Allow user to enter all details manually.

This is the easiest option and can be accomplished through the Jadu Directories
module, plus forms functionality. Simply put users would enter all relevant data into an
online form such as book title, a
uthor…etc. and their corresponding review (which could
be limited to a number of words/characters if you choose). This data can be routed for
approval or allowed to populate directly to the live system. Once in the system, it will be
fully searchable as
well as available for discovery in a robust A
-
Z tool.


Option #2: Allow Library staff to enter books into the system (such as the top 10
or 20 books of the week or month) and solicit reviews from the general public.

This is very similar to the option abov
e except users are not permitted to enter new
titles. They will simply be allowed to choose a book from a dropdown menu which has
been pre
-
populated by a member of Library staff. The rest of the functionality from #1
above then applies.


Option #3:
H
ave
all books in the library dynamically populate to the book field for
users query and selection.

Utilizing Jadu

s XForms Professional module, an Integrated Component could be
developed that allows the user to search a database of books / titles / ISBNs withi
n the
Form
and

select the chosen title, and provide any other details deemed suitable to be
built into this form, over which
Library staff has

total control over the questions
being

asking. This data can then be exported via the XForms Professional module
in a CSV
format for example, and then imported directly into a Jadu Directory that would provide
a single searchable directory of book reviews.


To clarify this explanation… We would need to build an integrator between your books


-

Questionnaire


26


database and our Xforms Pr
ofessional software and then port that information into Jadu
Directories. This option would be both time consuming and costly to implement.



Supporting an internal intranet, website is
something we are very interested in. Supporting an
intranet website
for staff only where documents can
be posted and shared, staff specific information is
listed and that is searchable would solve several
concerns and issues.


Jadu offers a full intranet product in addition to the CMS. To save on cost, some of our
client
s have utilized our Galaxies functionality which allows you to spawn a separate
CMS system. You can lock this second CMS down, requiring users to login to see the
content. Through this method you can basically have an Intranet system for free.



-

Questionnaire


27



NICE TO

HAVE ITEMS


While e
-
commerce capability is not necessary, as all
payment transactions are handled through a
separate site, having the option might serve a
purpose at some point in the future.


There is a full Ecommerce Jadu module available called Jadu
Retail.

Simplified publishing of web content to where it
takes no more than two mouse clicks would be
helpful.


When a content creator is ready to publish content, they simply need to press submit
the content for review (1 click). The Webmaster will the
n receive the content and only
needs to approve the content and make it “live” (2 clicks).

We would like to have the option to display
graphical site maps in site sections.



Websites powered using the Jadu CMS feature a dynamically generated site map as
standard. Links within individual section „landing pages‟ are also dynamically generated
and displayed to the site visitor as they navigate through the site.


Additional display options
can

be achieved through the use of custom front end
scripting.


The a
bility to suggest appropriate branch web pages
for patrons would be nice. This could be based upon
location of their IP address or the like.


We have government clients in which webpage content is served up based on location
(IP
-
driven). We also have extensive A
-
Z functionality for ease of finding content across
branch web pages.

The migration may include a redesign of the existing
website, wh
ich will be detailed through the course
of the selection process based upon input from
MCFL staff and vendor capabilities.


Jadu has award winning web designers on staff.



-

Questionnaire


28



ASSUMPTIONS AND CONSTRAINTS


Vendor bids may not exceed $40,000 for the total
implementation of the ne
w CMS solution. This
should include all costs to develop, implement and
launch the new CMS solution along with any
training, software licensing, and hardware expenses.


We recommend implementing

Jadu eXpress

with a perpetual license of

$25,000.


Our bid is for

$40,000

which will include Jadu eXpress ($25K) plus
$15K in
professiona
l services for implementation, project management

etc. required to
successfully implement the CMS Platform.




ALL task/job/policy data will be current and
approved as such by MCFL management.


Agreed

Training course ma
terials loaned to the vendor and
produced by the vendor will be in standard
American English.


Agreed

MCFL management will appoint one person
to serve
as a project coordinator/manager.


Great. This is actually a Jadu requirement for implementations.

MCFL CMS Selectors will provide appropriate
support documentation for the successful
comple
tion of the project.


Agreed

There will be no significant changes to the
task/job/policy data during the project.


Agreed

The vendor will provide technical support to the
MCFL support staff once the CMS is in use.


Agreed
. Customers have access to support.jadu.net


our
support portal for technical
a
nd non
-
technical support.



-

Questionnaire


29



The vendor shall warrant that on delivery, all media
containing the content of the CMS and training
material for the CMS to be free of material faults
and processing errors.


Agreed. T
h
is
will be in the contract. Note that this warranty co
mes with a reasonable
expiration period.

At the conclusion of the project, all materials
developed by the vendor specifically for MCFL will
become the exclusive property of MCFL. In addition,
any and all w
ork sheets and other working
documentation will also become the property of
MCFL.


Materials developed specifically for MCFL will be the property of MCFL.

When applicable, travel and lodging will be billed a
t
cost. Ground travel will be billed at the standard rate
used by MCFL. Air travel will be by coach with a
major U.S. airline. Lodging and meals will not exceed
$43.75 per day.


Agreed

When applicable, postage, UPS ground, overnight
delivery, and shipping charges will be billed at cost


Agreed

All telephone and data transmission charges will
not
be billable.



Understood

Billing for travel, lodging, meals, postage, shipping,
co
mmunications, et cetera, will be invoiced
separately at the end of each month and must be
approved in advance by MCFL management.


Understood



-

Questionnaire


30


SELECTION CRITERIA


Ease

of system use


Will be determined
by MCFL
through discussions, presentations and system
demonstrations

of the software by Jadu

to MCFL s
taff
.

Total cost to implement solution and reoccurring
annual costs


$40,000 total cost of license
and

Professional Services to implement.


Recurring costs are 20% of
current

license cost (in this case, $5,000 annual
reoccurring

cost).

Ability to integrate with Trumba, which uses
JavaScript and AJAX


For a full and seamless integration, a

Jadu

Homepages


widget could be developed to
present the Trumba calendar to website users on any Jadu
web
pages that this widget
was added to, removing the need for the standard

built
-
in

Jadu Events feature and
subsequent calendar widget.


A custom script would be required to then present the list of events within the context of
the main websites design, as is done on the following example page:
http://www.marinlibrary.org/news
-
and
-
events/calendar
-
of
-
events/?trumbaEmbed=date%3D20100928



This
will

result in a seamless integration of your Trumba solution to your
Jadu
-
powered

website.


Ability for vendor to assist in some or all of the
implementation including migration from existing
CMS solution with Hannon Hill, which uses two
Ubuntu ver. 2.6 severs and a MySQL database.


We will assist with implementati
on including project management and technical support.
Due to the budget cap it is unlikely tha
t we will be able to assist with actual content
migratio
n outside of the project management and guidance work.

Website redesign possibilities and suggestions on
how to improve our existing website.


Jadu is a full software shop including award winning web desi
gn.

We would need to
determine our ability to assist in website redesign as the $15K in professional services
is allocated.

Knowledge of Hannon Hill Cascade Server product to
aid in migration


We have a high level knowledge of the Hannon Hill Cascade Server p
roduct.

Thoroughness of training material


Our training
material

is extremely thorough


so
much so that it is a competitive
advantage for Jadu.



-

Questionnaire


31



Effective and concise communications both written
and oral from prospective vendor


We strive for effective &
concise

communications.
For MCFL

to
determine
.

Included software updates as part of annual
maintenance


As long as you are under a support agreement, software updates are included.

Proven p
r
oject manag
ement skills for delivery within
agreed upon deadlines


Jadu has dedicated highly experienced project managers with years of

successful

implementations under their belts.

Three or more years of experience in

o
Content management implementations,
mig
rations, and integrations with third party
applications via API

o
Dealing with digital archiving

o
Working with fast/optimized databases


We have
7
+

years

experience

in CMS implementations, migrations and integratio
ns,
archiving of digital content
as it relates to con
tent management
a
nd working with fast
and

dynamic

databases.