Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Dan Scott 
I've temporarily set up mirrors at:

* http://stuff.coffeecode.net/www.loc.gov/marc/ (MARC21 docs)
* http://stuff.coffeecode.net/www.loc.gov/standards/sourcelist/
(standards documentation)

Hopefully these won't be necessary for long, or at all :/

On Mon, Sep 30, 2013 at 5:13 PM, Kyle Banerjee  wrote:
> It appeared very recently (depending on your timeframe) -- but that version
> is absolutely necessary because the javascript support in 3.0 couldn't
> support what I needed to do. And I had no access to cgi at the time I wrote
> it, so server side action that might have accommodated Mosaic aficionados
> was out of the question...
>
> kyle
>
>
> On Mon, Sep 30, 2013 at 2:08 PM, Roy Tennant  wrote:
>
>> Netscape 4.0 is out? Gosh, but it sure is hard to keep up!
>> Roy
>>
>>
>> On Mon, Sep 30, 2013 at 2:06 PM, Kyle Banerjee > >wrote:
>>
>> > If all people need is to look up MARC tags, there is also the Cataloging
>> > Calculator http://calculate.alptown.com/  Unless you want to want to
>> feel
>> > totally disgusted, avoid looking source code as it was my first
>> javascript
>> > program which was cobbled together in a day (i.e. it is garbage) and
>> hasn't
>> > been gone through a substantial revision since 1997. The good news is
>> that
>> > if you're still on Netscape 4.0, it should work fine...
>> >
>> > kyle
>> >
>> >
>> > On Mon, Sep 30, 2013 at 1:56 PM, Roy Tennant 
>> wrote:
>> >
>> > > As seen on Twitter, OCLC also has our version of MARC documentation
>> here:
>> > >
>> > > 
>> > >
>> > > It's mostly exactly the same except for the places where we have
>> inserted
>> > > small but effective messages that "RESISTANCE IS FUTILE, YOU WILL BE
>> > > ASSIMILATED".
>> > > Roy
>> > >
>> > >
>> > > On Mon, Sep 30, 2013 at 1:31 PM, Becky Yoose 
>> wrote:
>> > >
>> > > > FYI - this also means that there's a very good chance that the MARC
>> > > > standards site [1] and the Source Codes site [2] will be down as
>> well.
>> > I
>> > > > don't know if there are any mirror sites out there for these pages.
>> > > >
>> > > > [1] http://www.loc.gov/marc/
>> > > > [2] http://www.loc.gov/standards/sourcelist/index.html
>> > > >
>> > > > Thanks,
>> > > > Becky, about to be (forcefully) departed with her standards
>> > documentation
>> > > >
>> > > >
>> > > > On Mon, Sep 30, 2013 at 11:39 AM, Jodi Schneider <
>> jschnei...@pobox.com
>> > > > >wrote:
>> > > >
>> > > > > Interesting -- thanks, Birkin -- and tell us what you think when
>> you
>> > > get
>> > > > it
>> > > > > implemented!
>> > > > >
>> > > > > :) -Jodi
>> > > > >
>> > > > >
>> > > > > On Mon, Sep 30, 2013 at 5:19 PM, Birkin Diana <
>> > birkin_di...@brown.edu
>> > > > > >wrote:
>> > > > >
>> > > > > > > ...you'd want to create a caching service...
>> > > > > >
>> > > > > >
>> > > > > > One solution for a relevant particular problem (not full-blown
>> > > > > linked-data
>> > > > > > caching):
>> > > > > >
>> > > > > > http://en.wikipedia.org/wiki/XML_Catalog
>> > > > > >
>> > > > > > excerpt: "However, if they are absolute URLs, they only work when
>> > > your
>> > > > > > network can reach them. Relying on remote resources makes XML
>> > > > processing
>> > > > > > susceptible to both planned and unplanned network downtime."
>> > > > > >
>> > > > > > We'd heard about this a while ago, but, Jodi, you and David
>> Riordan
>> > > and
>> > > > > > Congress have caused a temporary retreat from normal sprint-work
>> > here
>> > > > at
>> > > > > > Brown today to investigate implementing this!  :/
>> > > > > >
>> > > > > > The particular problem that would affect us: if your processing
>> > tool
>> > > > > > checks, say, an loc.gov mods namespace url, that processing will
>> > > fail
>> > > > if
>> > > > > > the loc.gov url isn't available, unless you've implemented xml
>> > > > catalog,
>> > > > > > which is a formal way to locally resolve such external
>> references.
>> > > > > >
>> > > > > > -b
>> > > > > > ---
>> > > > > > Birkin James Diana
>> > > > > > Programmer, Digital Technologies
>> > > > > > Brown University Library
>> > > > > > birkin_di...@brown.edu
>> > > > > >
>> > > > > >
>> > > > > > On Sep 30, 2013, at 7:15 AM, Uldis Bojars 
>> > > wrote:
>> > > > > >
>> > > > > > > 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

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Kyle Banerjee 
It appeared very recently (depending on your timeframe) -- but that version
is absolutely necessary because the javascript support in 3.0 couldn't
support what I needed to do. And I had no access to cgi at the time I wrote
it, so server side action that might have accommodated Mosaic aficionados
was out of the question...

kyle


On Mon, Sep 30, 2013 at 2:08 PM, Roy Tennant  wrote:

> Netscape 4.0 is out? Gosh, but it sure is hard to keep up!
> Roy
>
>
> On Mon, Sep 30, 2013 at 2:06 PM, Kyle Banerjee  >wrote:
>
> > If all people need is to look up MARC tags, there is also the Cataloging
> > Calculator http://calculate.alptown.com/  Unless you want to want to
> feel
> > totally disgusted, avoid looking source code as it was my first
> javascript
> > program which was cobbled together in a day (i.e. it is garbage) and
> hasn't
> > been gone through a substantial revision since 1997. The good news is
> that
> > if you're still on Netscape 4.0, it should work fine...
> >
> > kyle
> >
> >
> > On Mon, Sep 30, 2013 at 1:56 PM, Roy Tennant 
> wrote:
> >
> > > As seen on Twitter, OCLC also has our version of MARC documentation
> here:
> > >
> > > 
> > >
> > > It's mostly exactly the same except for the places where we have
> inserted
> > > small but effective messages that "RESISTANCE IS FUTILE, YOU WILL BE
> > > ASSIMILATED".
> > > Roy
> > >
> > >
> > > On Mon, Sep 30, 2013 at 1:31 PM, Becky Yoose 
> wrote:
> > >
> > > > FYI - this also means that there's a very good chance that the MARC
> > > > standards site [1] and the Source Codes site [2] will be down as
> well.
> > I
> > > > don't know if there are any mirror sites out there for these pages.
> > > >
> > > > [1] http://www.loc.gov/marc/
> > > > [2] http://www.loc.gov/standards/sourcelist/index.html
> > > >
> > > > Thanks,
> > > > Becky, about to be (forcefully) departed with her standards
> > documentation
> > > >
> > > >
> > > > On Mon, Sep 30, 2013 at 11:39 AM, Jodi Schneider <
> jschnei...@pobox.com
> > > > >wrote:
> > > >
> > > > > Interesting -- thanks, Birkin -- and tell us what you think when
> you
> > > get
> > > > it
> > > > > implemented!
> > > > >
> > > > > :) -Jodi
> > > > >
> > > > >
> > > > > On Mon, Sep 30, 2013 at 5:19 PM, Birkin Diana <
> > birkin_di...@brown.edu
> > > > > >wrote:
> > > > >
> > > > > > > ...you'd want to create a caching service...
> > > > > >
> > > > > >
> > > > > > One solution for a relevant particular problem (not full-blown
> > > > > linked-data
> > > > > > caching):
> > > > > >
> > > > > > http://en.wikipedia.org/wiki/XML_Catalog
> > > > > >
> > > > > > excerpt: "However, if they are absolute URLs, they only work when
> > > your
> > > > > > network can reach them. Relying on remote resources makes XML
> > > > processing
> > > > > > susceptible to both planned and unplanned network downtime."
> > > > > >
> > > > > > We'd heard about this a while ago, but, Jodi, you and David
> Riordan
> > > and
> > > > > > Congress have caused a temporary retreat from normal sprint-work
> > here
> > > > at
> > > > > > Brown today to investigate implementing this!  :/
> > > > > >
> > > > > > The particular problem that would affect us: if your processing
> > tool
> > > > > > checks, say, an loc.gov mods namespace url, that processing will
> > > fail
> > > > if
> > > > > > the loc.gov url isn't available, unless you've implemented xml
> > > > catalog,
> > > > > > which is a formal way to locally resolve such external
> references.
> > > > > >
> > > > > > -b
> > > > > > ---
> > > > > > Birkin James Diana
> > > > > > Programmer, Digital Technologies
> > > > > > Brown University Library
> > > > > > birkin_di...@brown.edu
> > > > > >
> > > > > >
> > > > > > On Sep 30, 2013, at 7:15 AM, Uldis Bojars 
> > > wrote:
> > > > > >
> > > > > > > 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.orgfor
> > > > > > 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).
> > > > > >

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Roy Tennant 
Netscape 4.0 is out? Gosh, but it sure is hard to keep up!
Roy


On Mon, Sep 30, 2013 at 2:06 PM, Kyle Banerjee wrote:

> If all people need is to look up MARC tags, there is also the Cataloging
> Calculator http://calculate.alptown.com/  Unless you want to want to feel
> totally disgusted, avoid looking source code as it was my first javascript
> program which was cobbled together in a day (i.e. it is garbage) and hasn't
> been gone through a substantial revision since 1997. The good news is that
> if you're still on Netscape 4.0, it should work fine...
>
> kyle
>
>
> On Mon, Sep 30, 2013 at 1:56 PM, Roy Tennant  wrote:
>
> > As seen on Twitter, OCLC also has our version of MARC documentation here:
> >
> > 
> >
> > It's mostly exactly the same except for the places where we have inserted
> > small but effective messages that "RESISTANCE IS FUTILE, YOU WILL BE
> > ASSIMILATED".
> > Roy
> >
> >
> > On Mon, Sep 30, 2013 at 1:31 PM, Becky Yoose  wrote:
> >
> > > FYI - this also means that there's a very good chance that the MARC
> > > standards site [1] and the Source Codes site [2] will be down as well.
> I
> > > don't know if there are any mirror sites out there for these pages.
> > >
> > > [1] http://www.loc.gov/marc/
> > > [2] http://www.loc.gov/standards/sourcelist/index.html
> > >
> > > Thanks,
> > > Becky, about to be (forcefully) departed with her standards
> documentation
> > >
> > >
> > > On Mon, Sep 30, 2013 at 11:39 AM, Jodi Schneider  > > >wrote:
> > >
> > > > Interesting -- thanks, Birkin -- and tell us what you think when you
> > get
> > > it
> > > > implemented!
> > > >
> > > > :) -Jodi
> > > >
> > > >
> > > > On Mon, Sep 30, 2013 at 5:19 PM, Birkin Diana <
> birkin_di...@brown.edu
> > > > >wrote:
> > > >
> > > > > > ...you'd want to create a caching service...
> > > > >
> > > > >
> > > > > One solution for a relevant particular problem (not full-blown
> > > > linked-data
> > > > > caching):
> > > > >
> > > > > http://en.wikipedia.org/wiki/XML_Catalog
> > > > >
> > > > > excerpt: "However, if they are absolute URLs, they only work when
> > your
> > > > > network can reach them. Relying on remote resources makes XML
> > > processing
> > > > > susceptible to both planned and unplanned network downtime."
> > > > >
> > > > > We'd heard about this a while ago, but, Jodi, you and David Riordan
> > and
> > > > > Congress have caused a temporary retreat from normal sprint-work
> here
> > > at
> > > > > Brown today to investigate implementing this!  :/
> > > > >
> > > > > The particular problem that would affect us: if your processing
> tool
> > > > > checks, say, an loc.gov mods namespace url, that processing will
> > fail
> > > if
> > > > > the loc.gov url isn't available, unless you've implemented xml
> > > catalog,
> > > > > which is a formal way to locally resolve such external references.
> > > > >
> > > > > -b
> > > > > ---
> > > > > Birkin James Diana
> > > > > Programmer, Digital Technologies
> > > > > Brown University Library
> > > > > birkin_di...@brown.edu
> > > > >
> > > > >
> > > > > On Sep 30, 2013, at 7:15 AM, Uldis Bojars 
> > wrote:
> > > > >
> > > > > > 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.orgfor
> > > > > 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  >
> > > > wrote:
> > > > > >
> > > > > >> Any best practices for caching authorities/vocabs to suggest for
> > > this
> > > > > >> thread on the Code

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Becky Yoose 
Cheers, deb!

>I was gonna say something about still being able to use LCSH and LCNAF via
Connexion, but that's really mostly for humans 

Well, at least for those who have Connexion in the first place ;c)

I'm trying to cover all the bases for those catalogers who are panicking
about Authorities and standards sites going dark tomorrow. Again, Wayback
Machine slipped my mind for the standards sites :cP Please forgive me - I
think I have a case of the Mondays...


On Mon, Sep 30, 2013 at 4:03 PM, Debra Shapiro  wrote:

> And of course http://dewey.info/ will still work no matter what the feds
> do …
>
> I was gonna say something about still being able to use LCSH and LCNAF via
> Connexion, but that's really mostly for humans 
>
> deb
>
>
> On Sep 30, 2013, at 3:58 PM, Becky Yoose wrote:
>
> > And the OCLC Seal of Approval...
> >
> >
> > On Mon, Sep 30, 2013 at 3:56 PM, Roy Tennant 
> wrote:
> >
> >> As seen on Twitter, OCLC also has our version of MARC documentation
> here:
> >>
> >> 
> >>
> >> It's mostly exactly the same except for the places where we have
> inserted
> >> small but effective messages that "RESISTANCE IS FUTILE, YOU WILL BE
> >> ASSIMILATED".
> >> Roy
> >>
> >>
> >>
>
> dsshap...@wisc.edu
> Debra Shapiro
> UW-Madison SLIS
> Helen C. White Hall, Rm. 4282
> 600 N. Park St.
> Madison WI 53706
> 608 262 9195
> mobile 608 712 6368
> FAX 608 263 4849
>

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Becky Yoose 
And the OCLC Seal of Approval...


On Mon, Sep 30, 2013 at 3:56 PM, Roy Tennant  wrote:

> As seen on Twitter, OCLC also has our version of MARC documentation here:
>
> 
>
> It's mostly exactly the same except for the places where we have inserted
> small but effective messages that "RESISTANCE IS FUTILE, YOU WILL BE
> ASSIMILATED".
> Roy
>
>
>

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Kyle Banerjee 
If all people need is to look up MARC tags, there is also the Cataloging
Calculator http://calculate.alptown.com/  Unless you want to want to feel
totally disgusted, avoid looking source code as it was my first javascript
program which was cobbled together in a day (i.e. it is garbage) and hasn't
been gone through a substantial revision since 1997. The good news is that
if you're still on Netscape 4.0, it should work fine...

kyle


On Mon, Sep 30, 2013 at 1:56 PM, Roy Tennant  wrote:

> As seen on Twitter, OCLC also has our version of MARC documentation here:
>
> 
>
> It's mostly exactly the same except for the places where we have inserted
> small but effective messages that "RESISTANCE IS FUTILE, YOU WILL BE
> ASSIMILATED".
> Roy
>
>
> On Mon, Sep 30, 2013 at 1:31 PM, Becky Yoose  wrote:
>
> > FYI - this also means that there's a very good chance that the MARC
> > standards site [1] and the Source Codes site [2] will be down as well. I
> > don't know if there are any mirror sites out there for these pages.
> >
> > [1] http://www.loc.gov/marc/
> > [2] http://www.loc.gov/standards/sourcelist/index.html
> >
> > Thanks,
> > Becky, about to be (forcefully) departed with her standards documentation
> >
> >
> > On Mon, Sep 30, 2013 at 11:39 AM, Jodi Schneider  > >wrote:
> >
> > > Interesting -- thanks, Birkin -- and tell us what you think when you
> get
> > it
> > > implemented!
> > >
> > > :) -Jodi
> > >
> > >
> > > On Mon, Sep 30, 2013 at 5:19 PM, Birkin Diana  > > >wrote:
> > >
> > > > > ...you'd want to create a caching service...
> > > >
> > > >
> > > > One solution for a relevant particular problem (not full-blown
> > > linked-data
> > > > caching):
> > > >
> > > > http://en.wikipedia.org/wiki/XML_Catalog
> > > >
> > > > excerpt: "However, if they are absolute URLs, they only work when
> your
> > > > network can reach them. Relying on remote resources makes XML
> > processing
> > > > susceptible to both planned and unplanned network downtime."
> > > >
> > > > We'd heard about this a while ago, but, Jodi, you and David Riordan
> and
> > > > Congress have caused a temporary retreat from normal sprint-work here
> > at
> > > > Brown today to investigate implementing this!  :/
> > > >
> > > > The particular problem that would affect us: if your processing tool
> > > > checks, say, an loc.gov mods namespace url, that processing will
> fail
> > if
> > > > the loc.gov url isn't available, unless you've implemented xml
> > catalog,
> > > > which is a formal way to locally resolve such external references.
> > > >
> > > > -b
> > > > ---
> > > > Birkin James Diana
> > > > Programmer, Digital Technologies
> > > > Brown University Library
> > > > birkin_di...@brown.edu
> > > >
> > > >
> > > > On Sep 30, 2013, at 7:15 AM, Uldis Bojars 
> wrote:
> > > >
> > > > > 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.orgfor
> > > > 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 
> > > 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
> > > >
> > >
> >
>

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Debra Shapiro 
And of course http://dewey.info/ will still work no matter what the feds do …

I was gonna say something about still being able to use LCSH and LCNAF via 
Connexion, but that's really mostly for humans 

deb


On Sep 30, 2013, at 3:58 PM, Becky Yoose wrote:

> And the OCLC Seal of Approval...
> 
> 
> On Mon, Sep 30, 2013 at 3:56 PM, Roy Tennant  wrote:
> 
>> As seen on Twitter, OCLC also has our version of MARC documentation here:
>> 
>> 
>> 
>> It's mostly exactly the same except for the places where we have inserted
>> small but effective messages that "RESISTANCE IS FUTILE, YOU WILL BE
>> ASSIMILATED".
>> Roy
>> 
>> 
>> 

dsshap...@wisc.edu
Debra Shapiro
UW-Madison SLIS
Helen C. White Hall, Rm. 4282
600 N. Park St.
Madison WI 53706
608 262 9195
mobile 608 712 6368
FAX 608 263 4849

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Roy Tennant 
As seen on Twitter, OCLC also has our version of MARC documentation here:



It's mostly exactly the same except for the places where we have inserted
small but effective messages that "RESISTANCE IS FUTILE, YOU WILL BE
ASSIMILATED".
Roy


On Mon, Sep 30, 2013 at 1:31 PM, Becky Yoose  wrote:

> FYI - this also means that there's a very good chance that the MARC
> standards site [1] and the Source Codes site [2] will be down as well. I
> don't know if there are any mirror sites out there for these pages.
>
> [1] http://www.loc.gov/marc/
> [2] http://www.loc.gov/standards/sourcelist/index.html
>
> Thanks,
> Becky, about to be (forcefully) departed with her standards documentation
>
>
> On Mon, Sep 30, 2013 at 11:39 AM, Jodi Schneider  >wrote:
>
> > Interesting -- thanks, Birkin -- and tell us what you think when you get
> it
> > implemented!
> >
> > :) -Jodi
> >
> >
> > On Mon, Sep 30, 2013 at 5:19 PM, Birkin Diana  > >wrote:
> >
> > > > ...you'd want to create a caching service...
> > >
> > >
> > > One solution for a relevant particular problem (not full-blown
> > linked-data
> > > caching):
> > >
> > > http://en.wikipedia.org/wiki/XML_Catalog
> > >
> > > excerpt: "However, if they are absolute URLs, they only work when your
> > > network can reach them. Relying on remote resources makes XML
> processing
> > > susceptible to both planned and unplanned network downtime."
> > >
> > > We'd heard about this a while ago, but, Jodi, you and David Riordan and
> > > Congress have caused a temporary retreat from normal sprint-work here
> at
> > > Brown today to investigate implementing this!  :/
> > >
> > > The particular problem that would affect us: if your processing tool
> > > checks, say, an loc.gov mods namespace url, that processing will fail
> if
> > > the loc.gov url isn't available, unless you've implemented xml
> catalog,
> > > which is a formal way to locally resolve such external references.
> > >
> > > -b
> > > ---
> > > Birkin James Diana
> > > Programmer, Digital Technologies
> > > Brown University Library
> > > birkin_di...@brown.edu
> > >
> > >
> > > On Sep 30, 2013, at 7:15 AM, Uldis Bojars  wrote:
> > >
> > > > 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 
> > 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
> > >
> >
>

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Becky Yoose 
Ah, I forgot about the Wayback Machine. Thank you :cD


On Mon, Sep 30, 2013 at 3:44 PM, Ford, Kevin  wrote:

> All *.loc.gov web sites will be "closed," including the two you quoted.
>
> The Internet Archive's Way Back Machine is probably your best bet for
> these types of things:
>
> http://web.archive.org/web/*/http://www.loc.gov/marc/
>
> http://web.archive.org/web/*/http://www.loc.gov/standards/sourcelist/index.html
>
> Yours,
> Kevin
>
> --
> Kevin Ford
> Network Development and MARC Standards Office
> Library of Congress
> Washington, DC
>
>
>

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Erik Hetzner 
At Mon, 30 Sep 2013 15:31:40 -0500,
Becky Yoose wrote:
> 
> FYI - this also means that there's a very good chance that the MARC
> standards site [1] and the Source Codes site [2] will be down as well. I
> don't know if there are any mirror sites out there for these pages.
> 
> Thanks,
> Becky, about to be (forcefully) departed with her standards documentation

Hi Becky,

Well, there’s always archive.org:

http://web.archive.org/web/20130816154112/http://www.loc.gov/marc/

best, Erik
Sent from my free software system .

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Ford, Kevin 
All *.loc.gov web sites will be "closed," including the two you quoted.

The Internet Archive's Way Back Machine is probably your best bet for these 
types of things:

http://web.archive.org/web/*/http://www.loc.gov/marc/
http://web.archive.org/web/*/http://www.loc.gov/standards/sourcelist/index.html

Yours,
Kevin

--
Kevin Ford
Network Development and MARC Standards Office
Library of Congress
Washington, DC


> -Original Message-
> From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Becky Yoose
> Sent: Monday, September 30, 2013 4:32 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will
> mean *.loc.gov is going offline October 1
> 
> FYI - this also means that there's a very good chance that the MARC
> standards site [1] and the Source Codes site [2] will be down as well.
> I
> don't know if there are any mirror sites out there for these pages.
> 
> [1] http://www.loc.gov/marc/
> [2] http://www.loc.gov/standards/sourcelist/index.html
> 
> Thanks,
> Becky, about to be (forcefully) departed with her standards
> documentation
> 
> 
> On Mon, Sep 30, 2013 at 11:39 AM, Jodi Schneider
> wrote:
> 
> > Interesting -- thanks, Birkin -- and tell us what you think when you
> get it
> > implemented!
> >
> > :) -Jodi
> >
> >
> > On Mon, Sep 30, 2013 at 5:19 PM, Birkin Diana  > >wrote:
> >
> > > > ...you'd want to create a caching service...
> > >
> > >
> > > One solution for a relevant particular problem (not full-blown
> > linked-data
> > > caching):
> > >
> > > http://en.wikipedia.org/wiki/XML_Catalog
> > >
> > > excerpt: "However, if they are absolute URLs, they only work when
> your
> > > network can reach them. Relying on remote resources makes XML
> processing
> > > susceptible to both planned and unplanned network downtime."
> > >
> > > We'd heard about this a while ago, but, Jodi, you and David Riordan
> and
> > > Congress have caused a temporary retreat from normal sprint-work
> here at
> > > Brown today to investigate implementing this!  :/
> > >
> > > The particular problem that would affect us: if your processing
> tool
> > > checks, say, an loc.gov mods namespace url, that processing will
> fail if
> > > the loc.gov url isn't available, unless you've implemented xml
> catalog,
> > > which is a formal way to locally resolve such external references.
> > >
> > > -b
> > > ---
> > > Birkin James Diana
> > > Programmer, Digital Technologies
> > > Brown University Library
> > > birkin_di...@brown.edu
> > >
> > >
> > > On Sep 30, 2013, at 7:15 AM, Uldis Bojars 
> wrote:
> > >
> > > > 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 
> > 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
> > >
> >

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Becky Yoose 
FYI - this also means that there's a very good chance that the MARC
standards site [1] and the Source Codes site [2] will be down as well. I
don't know if there are any mirror sites out there for these pages.

[1] http://www.loc.gov/marc/
[2] http://www.loc.gov/standards/sourcelist/index.html

Thanks,
Becky, about to be (forcefully) departed with her standards documentation


On Mon, Sep 30, 2013 at 11:39 AM, Jodi Schneider wrote:

> Interesting -- thanks, Birkin -- and tell us what you think when you get it
> implemented!
>
> :) -Jodi
>
>
> On Mon, Sep 30, 2013 at 5:19 PM, Birkin Diana  >wrote:
>
> > > ...you'd want to create a caching service...
> >
> >
> > One solution for a relevant particular problem (not full-blown
> linked-data
> > caching):
> >
> > http://en.wikipedia.org/wiki/XML_Catalog
> >
> > excerpt: "However, if they are absolute URLs, they only work when your
> > network can reach them. Relying on remote resources makes XML processing
> > susceptible to both planned and unplanned network downtime."
> >
> > We'd heard about this a while ago, but, Jodi, you and David Riordan and
> > Congress have caused a temporary retreat from normal sprint-work here at
> > Brown today to investigate implementing this!  :/
> >
> > The particular problem that would affect us: if your processing tool
> > checks, say, an loc.gov mods namespace url, that processing will fail if
> > the loc.gov url isn't available, unless you've implemented xml catalog,
> > which is a formal way to locally resolve such external references.
> >
> > -b
> > ---
> > Birkin James Diana
> > Programmer, Digital Technologies
> > Brown University Library
> > birkin_di...@brown.edu
> >
> >
> > On Sep 30, 2013, at 7:15 AM, Uldis Bojars  wrote:
> >
> > > 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 
> 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
> >
>

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Jodi Schneider 
Interesting -- thanks, Birkin -- and tell us what you think when you get it
implemented!

:) -Jodi


On Mon, Sep 30, 2013 at 5:19 PM, Birkin Diana wrote:

> > ...you'd want to create a caching service...
>
>
> One solution for a relevant particular problem (not full-blown linked-data
> caching):
>
> http://en.wikipedia.org/wiki/XML_Catalog
>
> excerpt: "However, if they are absolute URLs, they only work when your
> network can reach them. Relying on remote resources makes XML processing
> susceptible to both planned and unplanned network downtime."
>
> We'd heard about this a while ago, but, Jodi, you and David Riordan and
> Congress have caused a temporary retreat from normal sprint-work here at
> Brown today to investigate implementing this!  :/
>
> The particular problem that would affect us: if your processing tool
> checks, say, an loc.gov mods namespace url, that processing will fail if
> the loc.gov url isn't available, unless you've implemented xml catalog,
> which is a formal way to locally resolve such external references.
>
> -b
> ---
> Birkin James Diana
> Programmer, Digital Technologies
> Brown University Library
> birkin_di...@brown.edu
>
>
> On Sep 30, 2013, at 7:15 AM, Uldis Bojars  wrote:
>
> > 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  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
>

Re: [CODE4LIB] [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Birkin Diana 
> ...you'd want to create a caching service...


One solution for a relevant particular problem (not full-blown linked-data 
caching):

http://en.wikipedia.org/wiki/XML_Catalog

excerpt: "However, if they are absolute URLs, they only work when your network 
can reach them. Relying on remote resources makes XML processing susceptible to 
both planned and unplanned network downtime."

We'd heard about this a while ago, but, Jodi, you and David Riordan and 
Congress have caused a temporary retreat from normal sprint-work here at Brown 
today to investigate implementing this!  :/

The particular problem that would affect us: if your processing tool checks, 
say, an loc.gov mods namespace url, that processing will fail if the loc.gov 
url isn't available, unless you've implemented xml catalog, which is a formal 
way to locally resolve such external references.

-b
---
Birkin James Diana
Programmer, Digital Technologies
Brown University Library
birkin_di...@brown.edu


On Sep 30, 2013, at 7:15 AM, Uldis Bojars  wrote:

> 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  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

[CODE4LIB] Code4Lib Edmonton meetup

2013-09-30 Thread Sam Popowich 
Apologies for cross-posting.

Code4Lib Edmonton will be meeting this Thursday, October 3rd, at 6pm at the
Empress Ale House, 9912 82 (Whyte) Avenue. In addition to chatting about
library technology related things, we'll start organizing a lightning talk
even to be held in November. More details will follow Thursday's meetup.

Code4Lib is open to anyone interested in library technology, discovery,
metadata, programming, etc. If any of these things sound interesting to
you, feel free to show up. If you have any questions about Code4Lib
Edmonton, please let me know. Code4Lib Edmonton is also on Twitter
@code4libYEG.

Thanks,
Sam.

-- 

Sam Popowich

Discovery Systems Librarian

University of Alberta Library

Edmonton, Alberta

sam.popow...@ualberta.ca

780-492-8215

Re: [CODE4LIB] Fwd: [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Karen Coyle 
I don't know of any best practices *yet* but for various reasons it 
seems to me that a network of mirrors that push updates out would be a 
good thing. Even not considering major government disfunctionality, 
there are fires and floods and earthquakes and ... etc. It's never 
sufficient to rely on one copy.[1]


Although I'm glad the torrent is there, the API functionality is 
probably the most used.


kc
[1] cf. University of California keeps two physical storage sites for 
last(2) copies of books - one in the North, one in the South - both 
prone to earthquakes, but very very unlikely at the same time because 
they are on different major fault lines, and about 400 miles apart.


On 9/30/13 4:15 AM, Uldis Bojars wrote:

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  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 
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_Labs
davidrior...@nypl.org | m 203.521.1222 | @riordan<
http://twitter.com/riordan>




--
Karen Coyle
kco...@kcoyle.net http://kcoyle.net
m: 1-510-435-8234
skype: kcoylenet

Re: [CODE4LIB] Code4Lib 2014: Save the dates!

2013-09-30 Thread Jodi Schneider 
Conference info isn't prominent on the homepage (I just had to look it up
to share with somebody).

Anybody have time to put the Code4Lib 2014 dates & schedule there
prominently? Ideally along with proposal deadlines...

/me ducks
-Jodi


On Fri, Jun 28, 2013 at 8:31 PM, Tim McGeary  wrote:

> Hi all,
>
> I am happy to announce that we have secured the venue and dates for
> Code4Lib 2014!  The conference will be held at the Sheraton Raleigh Hotel
> in downtown Raleigh, NC on March 24 - 27, 2014.  Preconferences will be
> held Monday March 24, and the main conference on Tuesday March 25 - 27.
>
> The Sheraton Raleigh Hotel is working through a $6 million renovation that
> will be completed this fall.  Upon your arrival, you will find warm and
> open lobby, great for informal meetups and relaxing.   In the hotel will be
> Jimmy V's restaurant, where 5% of the revenues are donated to the V
> Foundation for Cancer Research.  The hotel is always within easy walking
> distance to many restaurants, pubs, parks, museums, and other attractions.
>
> The Code4Lib 2014 Conference will be the only event using the meeting space
> this week.  The meeting space offers open foyers that will be excellent for
> our morning and afternoon breaks, along with space for the project and
> vendor table sponsors looking to build collaboration with the Code4Lib
> community.
>
> Finally, the hotel has the capacity to host all of the attendees, and we've
> negotiated a rate of $159/night that includes wireless access in the hotel
> rooms.  Hotel reservations will be able to made after you register using
> the information provided in your registration confirmation.  We will be
> publishing more details as become available.
>
> Finally, we could not have reached this point without the effort of
> CONCENTRA Conference Management Services.  The contract negotiation process
> took a great deal of effort and had a few unexpected turns.  Having
> CONCENTRA steer the process was just what we needed to get a contract that
> is fair and appropriate for Code4Lib.
>
> We are looking forward to hosting you in North Carolina next spring!
>
> Cheers,
> Tim
>
> --
> Tim McGeary
> Director of Library & Information Technology
> University of North Carolina at Chapel Hill
> tim.mcge...@unc.edu
> timmcge...@gmail.com
> GTalk/Yahoo/Skype/Twitter: timmcgeary
>

[CODE4LIB] edUi Discount

2013-09-30 Thread EdUI Conference 
Registrations for the edUi conference are going gangbusters. Even if you
missed out on our early bird tickets, Code4Lib subscribers can still
register for $450.

Just use the discount code 'library' when you
register
.

Some sessions Code4Lib subscribers might want to check out include:

   - Reading, Writing, and Research in the Digital Age
   

   Plenary By Kathryn Zickuhr
   - Responsive Design: An Undead Introduction
    By
   John Rhea 
   - Mobile for Dinosaurs
    By Warren
Craghead
   - This is How You Do Digital Collections in 2013
   

By
   Sean Hannan , Steven
Heslip
   - Stop Reinventing the Wheel: Faster Web Development Using Bootstrap
   Framework
   

By
   Gaurav Gupta 
   - Geo-discovery of Library Collections with Google Glass
   

By
   Doug Chestnut , Steve
   Johnson 
   - Designing for Information Objects
    By Duane
   Degler , Neal
Johnson

Registration includes a half-day
workshop
.

Hope to see you in Richmond, VA this November.

-Trey

[CODE4LIB] Fwd: [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Jodi Schneider 
FYI... A torrent in a bagit, courtesy of dchud. -J

-- Forwarded message --
From: Dan Chudnov 
Date: Mon, Sep 30, 2013 at 12:16 PM
Subject: Re: [CODE4LIB] HEADS UP - Government shutdown will mean
*.loc.govis going offline October 1
To: Jodi Schneider 
Cc: Uldis Bojars , Nuno Lopes 


Hi all, and thanks for thinking of this, Jodi.  I guess I gave a few talks
on this 3-4 years ago, but haven't done much with it since.

With the shutdown pending, though, it seemed a good idea to grab id.loc.gov's
latest data downloads.  Here's a torrent file of all those zip files, in a
bagit bag:


http://dchud_at_umich_edu-server_backup.s3.amazonaws.com/20130930-id.loc.gov-data.tar.gz?torrent

"First, grab the data before it disappears..." :)

Best, -Dan

On Sep 30, 2013, at 6:56 AM, Jodi Schneider  wrote:

> I think that makes sense -- maybe send this to Code for Libraries <
CODE4LIB@listserv.nd.edu> ?
>
> dchud had talked about this at one point -- not sure if there's anything
going on now?
>
> :) -Jodi
>
>
> On Mon, Sep 30, 2013 at 11:46 AM, Uldis Bojars  wrote:
> 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.orgfor 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  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 
> 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_Labs<http://twitter.com/nypl_labs>
> davidrior...@nypl.org | m 203.521.1222 | @riordan<
http://twitter.com/riordan>
>
>
>

[CODE4LIB] Fwd: [CODE4LIB] HEADS UP - Government shutdown will mean *.loc.gov is going offline October 1

2013-09-30 Thread Uldis Bojars 
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  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 
> 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_Labs
> davidrior...@nypl.org | m 203.521.1222 | @riordan<
> http://twitter.com/riordan>
>
>

[CODE4LIB] Fwd: [Dbworld] 1st Workshop on long term preservation for big scientific data

2013-09-30 Thread Jodi Schneider 
Chicago workshop on scientific data preservation -- please share as
appropriate. -Jodi

-- Forwarded message --
From: Salima Benbernou 
Date: Mon, Sep 30, 2013 at 10:08 AM
Subject: [Dbworld] 1st Workshop on long term preservation for big
scientific data
To: dbwo...@cs.wisc.edu


***

                         C A L L   F O R
  P A P E R S

Â1st Workshop on LOng term Preservation for big
Scientific data  (LOPS 2014)


http://lipade.math-info.univ-paris5.fr/lops/
                              Â
 In conjunction with the IEEE International Conference on
Data Engineering (ICDE 2014)

  March, 31 - April 4, 2014 - Chicago,
IL, USA


***

- Aim :

Scientific data collected with modern sensors or dedicated detectors exceed
very often the perimeter of the initial scientific design in different
application domains. These data including experiments and simulations are
obtained more and more frequently with large material and human efforts.Â
For instance high energy physics and astrophysics experiments involve
multi-annual developments. Hence, the preservation of big data sets
produced is of permanent concern and has been addressed in various
disciplines at different levels. However, the challenge of digital
preservation of scientific data lies in the need to preserve not only the
dataset itself but also the ability it has to deliver knowledge to future
user community. A real scientific research asset allows future users to
reanalyze the data within new contexts. In fact, the data should be
preserved long term such that the access and the re-use are made possible
and lead to an enhancement of the initial investment. It is!
  therefore of outmost importance to pursue coherent and vigorous
approaches to preserve the scientific data at long term.

The overall goal of the workshop is to provide a forum for researchers to
sharing original ideas, discussing and refining future research challenges
in digital longevity of big scientific data in different application
domains.

- Topics of Interest :

The topics of interest for LOPS include, but are not limited to:

- Scientific data storage for long term digital preservation
- Long term experiments and simulation representation
- Long term data preservation for scientific workflows
- Accessing long term digitalized scientific data
- Data quality of long term digital preservation
- Privacy and security of scientific data
- Re-using approaches for scientific data
- Data Provenance for long term digital preservation
- Semantic to scientific data for long term digital preservation

- Paper submission :

Authors are invited to submit original, unpublished research papers that
are not being considered for publication in any other workshops.

Papers submissions are limited to maximum 8 pages, formatted according to
the ICDE formatting guidelines.

All papers should be submitted in PDF format using the Workshop online
submission system at : https://cmt.research.microsoft.com/LOPS2014

The papers from the workshop will be published in the ICDE proceedings and
will become available through the IEEE Xplore.

- Important Dates :

* Submission deadline: November 10, 2013
* Author notification: December 13, 2013
* Camera-ready papers due: December 20, 2013
* Workshop: April 4, 2014

- Workshop Co-Chairs

* Salima Benbernou, Université Paris Descartes, France
* Cristinel Diaconu, CPPM, France

- Program committee :

* Walid Aref, Purdue University, USA
* Mike Atallah, Purdue University, USA
* Laure Berti-Equille, IRD, France
* Claudia Bauzer Medeiros, University of Campinas,Brazil
* Gill Dobbie, University of Auckland, New Zealand
* Schahram Dustdar, Technic University of Vienna, Austria
* Aris Gkoulalas-Divanis, IBM, Ireland
* Therese Libourel, University of Montpellier, France
* Renee Miller, University of Toronto, Canada
* Mourad Ouzzani, QCRI, Qatar
* Mourad Ouziri, Université Paris Descartes, France
* Themis Palpanas, University of Trento, Italy
* Pierre Senellart, Télécom ParisTech, France
___
Please do not post msgs that are not relevant to the database community at
large.  Go to www.cs.wisc.edu/dbworld for guidelines and posting forms.
To unsubscribe, go to https://lists.cs.wisc.edu/mailman/listinfo/dbworld