Does anyone have any suggestions as to where the library should or should
not compromise when it comes to using an institutional CMS rather than a
custom library one? We are going through this process right now. Our web
pages are currently all in static HTML and LibGuides. I am wanting to move
to
You could do something like what I did and run your own data backend and use
whatever you need to/have to to display content.
Our website is just static HTML, CSS, and Javascript. Everything
dynamic/data-powered is javascript that is pulling from a centralized API
(written using grape:
for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Joshua
Welker
Sent: Wednesday, August 14, 2013 9:21 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Separate library CMS systems vs Campus-wide CMS systems
(was [CODE4LIB] LibGuides: I don't get it)
Does anyone have any suggestions
Why can't it be both? Just because the library has its own Web server
(something I would never, ever give up, mostly for Michael's reason #5),
that doesn't mean some of the library's content can't be part of the main
institutional Web site. That's what we do here. All of the relatively
static
That's an interesting idea. Do you run into performance issues with the
abundance of DOM updates with the javascript? Also, how much control do you
have over the content of library pages on the CMS?
Josh Welker
On Aug 14, 2013, at 8:35 AM, Sean Hannan shan...@jhu.edu wrote:
You could do
@LISTSERV.ND.EDU
Subject: [CODE4LIB] Separate library CMS systems vs Campus-wide CMS systems
(was [CODE4LIB] LibGuides: I don't get it)
Does anyone have any suggestions as to where the library should or should not
compromise when it comes to using an institutional CMS rather than a custom
library
Not really that I can see. Since I maintain the API, I maintain the API
responses and I only return what is necessary for display and interaction.
For example, our Service Location Hours
(http://www.library.jhu.edu/hours.html) are all managed in separate Google
Calendar calendars. The GCal API
Avoid Contribute, if possible. A Dreamweaver and Contribute framework
makes for a very flexible website. But... the Contribute editor accounts
have to be very locked down or else there will be some problems with the
two programs playing together. In Contribute, it is possible to enable
editing
: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Wilhelmina Randtke
Sent: Wednesday, August 14, 2013 10:32 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Separate library CMS systems vs Campus-wide CMS
systems (was [CODE4LIB] LibGuides: I don't get it)
Avoid Contribute
