I just wanted to, again, say thanks, in no particular order, to
- The organizers
- The presenters
- The volunteers
- The streamers
- The people who voted on presentations (even though mine didn't make
it, next time I'll make sure my entry starts with an 'A' and not a 'W')
-
+1. :)
On Fri, Feb 10, 2012 at 9:28 AM, Patrick Berry pbe...@gmail.com wrote:
I just wanted to, again, say thanks, in no particular order, to
- The organizers
- The presenters
- The volunteers
- The streamers
- The people who voted on presentations (even though mine didn't make
Gee I didn't know it was your room. Thanks for sharing!
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Patrick
Berry
Sent: Friday, February 10, 2012 12:29 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Thanks for everything
I just wanted
So, one question I forgot to toss out at the Ask Anything session is:
When do you know you have enough metadata?
You'll know it when you have it, isn't the response I'm looking for. So,
I'm sure you're wondering what the context for this question is, and
honestly there is none. This is geared
I think the answer is make sure you are able to add new elements to the
store later, and keep around your source data and plan to be able to
reprocess it. Something like what XC is doing. That way, you get to be
agile at the beginning and just deal with what you *know* is absolutely
needed, and
An interface is only as useful as the metadata allows it to be, and the
metadata is only as useful as the interface built to take advantage of it.
Ethan
On Fri, Feb 10, 2012 at 4:10 PM, David Faler dfa...@tlcdelivers.com wrote:
I think the answer is make sure you are able to add new elements
Ditto, and thank you, too. :)
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Patrick Berry
Sent: Friday, February 10, 2012 11:29 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Thanks for everything
I just wanted to, again, say thanks, in
Patrick:
I can only ask: enough for what? If you haven't a solid idea of what you
want the metadata to do, it's hard to evaluate either quantity or quality.
Metadata is not static--if it's not regularly evaluated, improved and added
to, it tends to lose its value and usefulness over time.
Hej hej,
Is anyone is using neo4j in their library projects.
If the answer is ja, I would be very interested in hearing how it's going.
How are you using it?
Is it something that is in production and is adding value or is it
more a skunkworks-type effort?
What languages are you using? Are you
Thanks everyone for the days packed with interesting discussions. It was
a great experience and I've already been talking to some people about
plans for Chicago awesomeness.
I remember a presentation where someone, perhaps Mike Schultz
http://code4lib.org/conference/2012/schultz said they
I think it was Tom Burton-West's talk on the first day (just getting my
notes in order, too):
http://code4lib.org/conference/2012/burton-west
His slides are linked there (thanks, Tom!).
wayne
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On
Hi,
AustLit ( http://www.austlit.edu.au ) is in the early stages of a
migration from javaServlets/xslt/oracle to java/neo4j/gremlin. The
web version of AustLit was developed in 2000 based on FRBR with a
strong emphasis on events realised with a topic map model, so the sql
implementation is close
Expanding on Diane's enough for what?, I see a lot of gradations
possible in this task.
Minimally, I can establish entity records for three persons, each of
whom is assigned a unique ID:
John Smith, ID=123
John Smith, ID=456
John Smith, ID=789
I decide to do this because I have three
My take on enough for what? is this:
What use cases do you have, both current and future? What sorts of queries
and data displays are necessary and sufficient to fulfill those use cases?
The collection of metadata involved in those displays and queries
constitutes enough.
Of course, this is
I have to say that the biggest thing is that there is never enough so get
use to the fact you always have to go back and adjust.
You could try to over think it and come up with use cases…
And you will potentially have spent time and money on data you are keeping
for no reason and still be missing
The whole advantage of RDF is that you can pull properties from different
vocabularies (as long as they're not logically disjoint). So, assuming your
richer ontology is some kind of RDF vocabulary, this exactly *what* you should
be doing.
-Ross.
On Feb 10, 2012, at 4:31 PM, Ethan Gruber
Hi Ross,
No, the richer ontology is not an RDF vocabulary, but it adheres to linked
data concepts.
I'm looking to do something like this example of embedding mods in rdf:
http://www.daisy.org/zw/ZedAI_Meta_Data_-_MODS_Recommendation#RDF.2FXML_2
These semantic ontologies are so flexible, it
17 matches
Mail list logo
