Hopefully I have not stepped upon any toes, but I was looking to add my name to
the roster and the page didn't exist. So I created it!
http://wiki.code4lib.org/index.php/2012_Lightning_Talks_Signup
It is basically a copy of what we used for 2011 and 2010 and 2009 and...
--Joel
Joel Richard
I won't speak on behalf of the organizers, but my recollection is that
signups for lightning talks on a given day are typically opened the day
before. I think there was some kerfuffle related to this last year (I seem
to recall it opening early and causing some confusion). But I suppose this
is
Personally, I would prefer to hold off on signing up for lightning
talks until the conference is actually underway...
$0.02,
Mark
On Wed, Jan 25, 2012 at 7:51 AM, Richard, Joel M richar...@si.edu wrote:
Well, if things have changed from last year, the page can be updated to
reflect the new
Hi Nathan,
It looks like your architectural thinking includes a management layer (DSpace,
Islandora, other...) and a storage layer.
For a storage layer that provides bit level preservation, more copies, up to a
point, is a good idea. For much disk storage, people go with 2 copies - a copy
on
Hi all,
For our preconference, “Digging into Metadata,” we’d like to get a little
discussion going to build on once the preconference rolls around.
A good part of our discussion will focus on metadata issues and how folks
have worked through said issues or have utilized metadata in an unique way
Are you upset because you missed the JCDL 2012 call for full papers? Don't fret
because the Program Committee has extended the deadline through next Tuesday,
January 30 to align with the call for short papers, etc. That means you still
have five days to submit something! For details see
I will contribute one particularly heartbreaking bit from my own
current metadata saga - I'm in one of these hybrid museum/research
library institutions where the library side has a aging MARC catalog
with its own issues that I won't go into at the moment. The museum
side has a commercial
For our preconference, “Digging into Metadata,” we’d like to get a little
discussion going to build on once the preconference rolls around.
...
- Dealing with free text in MARC records and how to parse them w/o too much
heartache
You can find horrendous stories even with data that's fully
On 2012-01-25, at 10:06 AM, Becky Yoose wrote:
- Dirty data issues when switching discovery layers or using legacy/vendor
metadata (ex. HathiTrust)
I have a sharp recollection of a slide in a presentation Roy Tennant offered up
at Access (at Halifax, maybe), where he offered up a range of
I was part of a particularly long siege during the METS offensive back in '08.
It was brutal. We pretty much ran out of everything and were fighting
hand-to-hand before the whole thing was over.
I remember toward the end, while out on requirement gathering patrol, my team
came up on a group of
+1
On Wed, Jan 25, 2012 at 4:36 PM, Jonathan Rochkind rochk...@jhu.edu wrote:
On 1/25/2012 1:13 PM, Kyle Banerjee wrote:
itself. For example, there's a system used for many digital archives that
splits a field in two anytime a field that needs to be represented by an
XML entity is
http://journal.code4lib.org/articles/4438
see KOHA section.
Markus Fischer
Am 25.01.2012 22:47, schrieb Ethan Gruber:
+1
On Wed, Jan 25, 2012 at 4:36 PM, Jonathan Rochkindrochk...@jhu.edu wrote:
On 1/25/2012 1:13 PM, Kyle Banerjee wrote:
itself. For example, there's a system used for
Thanks for the advice so far, everyone. Any recommendations for processors
and amount of RAM?
Nathan
On Wed, Jan 25, 2012 at 11:33 AM, Nate Vack njv...@wisc.edu wrote:
On Tue, Jan 24, 2012 at 11:21 AM, Nathan Tallman ntall...@gmail.com
wrote:
My institution is going to be purchasing a
Code4Lib Conference Attendees,
You voted with your (virtual) feet... so, with approval from conference
planners, we have rethought our preconference offering formerly known as
Hacking Content. It is now scheduled for the morning only and has a more
descriptive title. Feel free to join us.
Salvete!
*Warning Ranty. Brooke's Ideas shouldn't actually be consumed by anyone,
ever.*
Why are we so eager to 'protect the guilty' in discussions like this?
Our reluctance to share info on problems with software we use (because of
fear
of offending the vendor?) means that it's
Why are we so eager to 'protect the guilty' in discussions like this?
Why can't we just share this stuff in public and tell it like it is, so
the information is available for people who need it?
I agree that the practice is unfortunate as I personally believe that
critics are the
Kyle Banerjee writes
Our profession is very risk averse.
But fortunately we don't have any stereotypes around here. ;-)
Isn't the vendor the one the name of which starts with O, and the
product name ends with M?
Cheers,
Thomas Krichel
17 matches
Mail list logo
