Re: [CODE4LIB] Jobs Digest - I definitely didn't rip off someone else's job posting
Yes. Job postings are quite similar to one another (expect for the
Tennant's Treehouse posting of course). Discussions can be more interesting
and diverse :)
Uldis
On 29 May 2014 15:34, Jonathan Rochkind rochk...@jhu.edu wrote:
Is there anyone that found the original job postings to the list actually
MORE distracting and inconveniencing than the incessant discussion of what
to do about them?
Jonathan
On 5/29/14 7:44 AM, Ross Singer wrote:
THIS IS NOT EXACTLY WHAT WE AGREED TO
On May 29, 2014 7:38 AM, Andreas Orphanides akorp...@ncsu.edu wrote:
YAY FULL JOB POSTINGS
On Wed, May 28, 2014 at 11:40 PM, BWS Johnson
abesottedphoe...@yahoo.com
wrote:
Research Analyst I
Royt's Treehouse
The prestigious Tennant's Treehouse is accepting applications for the
position of Research Analyst I for the Juniper Club Library. A
collaborative position in nature, the Research Analyst I will indenture
themselves to the library duhrector artisanally collecting redundant
data
via Diebold-O-Tron. The Research Analyst I will be abused at any given
opportunity, be paid only in hard liquor, maintain all digital object
collections, regardless of relevance or irrelevance of said collection
and
shepherd digital humanities projects, whatevertheheckthoseare.
The successful candidate will have 17 years experience in Koha despite
this being an entry level position that only freshly minted graduates
may
apply to and that proficiency not possibly existing in this reality,
archiving meaningless discussion threads, ragging on royt at any given
opportunity, and collating mimeographs since we forgot to take this out
of
our job description sometime when MARC was merely a glimmer in a data
nerd's eye. None of these skills relate in the slightest to counting
votes,
but that's what HR told us, and ours is not to reason why.
We will not tell you where Royt's Treehouse is located since you are
meant
to already know. As with conference, you were meant to apply for this
post
prior to it making the rounds in your hemisphere, so if you are located
outside of the continental United States, too damn bad.
For further information, feel free to contact
abesottedphoe...@yahoo.com
,
where your email will fester in a pile since your résumé will be thrown
out
for having a funny name or not matching spurious keywords.
All applicants are REQUIRED to have a beating a dead horse Code{4}Lib
t-shirt.
[CODE4LIB] Fwd: [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1
What are best practices for preventing problems in cases like this when an important Linked Data service may go offline? --- originally this was a reply to Jodi which she suggested to post on the list too --- A safe [pessimistic?] approach would be to say we don't trust [reliability of] linked data on the Web as services can and will go down and to cache everything. In that case you'd want to create a caching service that would keep updated copies of all important Linked Data sources and a fall-back strategy for switching to this caching service when needed. Like archive.org for Linked Data. Some semantic web search engines might already have subsets of Linked Data web cached, but not sure how much they cover (e.g., if they have all of LoC data, up-to-date). If one were to create such a service how to best update it, considering you'd be requesting *all* Linked Data URIs from each source? An efficient approach would be to regularly load RDF dumps for every major source if available (e.g., LoC says - here's a full dump of all our RDF data ... and a .torrent too). What do you think? Uldis On 29 September 2013 12:33, Jodi Schneider jschnei...@pobox.com wrote: Any best practices for caching authorities/vocabs to suggest for this thread on the Code4Lib list? Linked Data authorities vocabularies at Library of Congress (id.loc.gov) are going to be affected by the website shutdown -- because of lack of government funds. -Jodi -- Forwarded message -- From: David Riordan davidrior...@nypl.org Date: Sat, Sep 28, 2013 at 3:08 PM Subject: [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1 To: CODE4LIB@listserv.nd.edu http://arstechnica.com/tech-policy/2013/09/library-of-congress-says-it-will-take-its-site-offline-if-govt-shuts-down/ This morning's latest terrifying news on the government shutdown front is that unless Congress decides to (ahahahahahah) oh who am I kidding. Broadcast message from root October 1, 2013 00:00 The system is going down for system halt NOW! Since the Library of Congress' web services are you know, won't have money, they'll be taken offline along with the rest of LC. Compared to most of the things that'll happen, this won't be so bad. However it could make a lot of people on this list's lives a living hell on Tuesday morning when we start getting system failures because an API relied on a lookup to id.loc.gov or any other LC service. So brace your bosses and patrons. Because without loc.gov, things could get weird. Seriously, if anyone knows more, please share. David Riordan | Product Manager, NYPL Labs | @NYPL_Labshttp://twitter.com/nypl_labs davidrior...@nypl.org | m 203.521.1222 | @riordan http://twitter.com/riordan
