The main page (http://wiki.code4lib.org/Main_Page) is displaying as
blank, and the history does not indicate any changes that would cause it
to be so. In fact, the history for EARLIER changes (eg, my change to
remove the new! text from the link to C4LN) are not displaying
properly in the
Could a glitch in the last upgrade be the culprit?
http://www.mediawiki.org/wiki/Thread:Project:Support_desk/Pages_not_displaying_properly
Best regards,
*Jason Bengtson, MLIS, MA*
Head of Library Computing and Information Systems
Assistant Professor, Graduate College
Department of Health
Jason et al.,
It looks like the problem was introducing a new category:
http://screencast.com/t/mXqaLDuiz4q
I reverted the main page back to the edits done on February 12th. The only
thing lost was the the c4l16 changes.
Thanks,
Becky
On Thu, Feb 26, 2015 at 10:08 AM, Jason Bengtson
Yeah, something must have happened with the last edit. However, when I
compare the two revisions before the last one, the diffs show up fine on my
end:
http://wiki.code4lib.org/index.php?title=Main_Pagediff=42811oldid=42726
I'll hold off on doing the undo option for the last edit to see if that
Any chance you have another LogFormat directive somewhere later in
config.txt or any file includes through the IncludeFile directive? If
there are multiples, the last one wins.
Chris Zagar
Librarian
Estrella Mountain Community College
-Original Message-
From: Code for Libraries
On Feb 26, 2015, at 9:48 AM, Owen Stephens o...@ostephens.com wrote:
I highly recommend Chapter 6 of the Linked Data book which details different
design approaches for Linked Data applications - sections 6.3
(http://linkeddatabook.com/editions/1.0/#htoc84) summarises the approaches as:
I apologize to both lists for this observation. I don't mean to offend anyone,
and now it's clear to me that this will potentially do so. I don't plan on
commenting further. I do hold both new technologists and traditional
librarians in respect - I just may generalize too much in trying to
So the issue being discussed on AUTOCAT was the availability/fault tolerance of
the database, given that it's spread over numerous remote systems, and I
suppose local caching and mirroring are the answers there.
The other issue was skepticism about the feasibility of indexing all these
I highly recommend Chapter 6 of the Linked Data book which details different
design approaches for Linked Data applications - sections 6.3
(http://linkeddatabook.com/editions/1.0/#htoc84) summarises the approaches as:
1. Crawling Pattern
2. On-the-fly dereferencing pattern
3. Query federation
On Feb 25, 2015, at 3:12 PM, Sarah Weissman seweiss...@gmail.com wrote:
I am kind of new to this linked data thing, but it seems like the real
power of it is not full-text search, but linking through the use of shared
vocabularies. So if you have data about Jane Austen in your database and
On Feb 25, 2015, at 2:48 PM, Esmé Cowles escow...@ticklefish.org wrote:
In the non-techie library world, linked data is being talked about (perhaps
only in listserv traffic) as if the data (bibliographic data, for instance)
will reside on remote sites (as a SPARQL endpoint??? We don't know
The OAI9 Workshop on Current Developments in Scholarly Communication
is taking place in the University of Geneva and in CERN, Geneva, on
17-19 June 2015. The meeting's web site is
http://indico.cern.ch/event/332370/
There are six plenary sessions
* Technical developments
*
We’ve had a fantastic number of responses and In the interest of saving the
other C4L subscriber’s bandwidth, we are going to contact everyone who
contacted us with a separate email including instructions so we can scale this!
If you still want to jump in we’d be happy to hear from you: just
13 matches
Mail list logo
