Hullo.
I'm interested to hear about people's approaches for modeling
repository objects in a normalized, spec-agnostic way, _relational_ way
while
maintaining the ability to cast objects as various specs (MODS, Dublin
Core).
People often resort to storing an object as one specification (the text
Hi Stephen,
I believe the UCSD folks have put things in a relational database in a
spec-agnostic way (and then they can pull things out as MODS, MARC, or
whatever on the fly when needed). There is a link below to their GitHub
repository which has some documentation (and slides from a 2013
We do store our metadata in a relational database (postgresql). But instead of
doing relational modeling of any particular schema, we model everything as RDF.
So our database is just one big table with columns for subject, prediate,
object and namedGraph. We do queries using Jena to
...@sobekdigital.com
352-682-9692 (mobile)
From: Code for Libraries CODE4LIB@LISTSERV.ND.EDU on behalf of Stephen Schor
stephensc...@nypl.org
Sent: Friday, April 17, 2015 1:27 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Modeling a repository's objects
, 2015 1:27 PM
To: CODE4LIB@LISTSERV.ND.EDU javascript:;
Subject: [CODE4LIB] Modeling a repository's objects in a relational
database
Hullo.
I'm interested to hear about people's approaches for modeling
repository objects in a normalized, spec-agnostic way, _relational_ way
while
...@nypl.org javascript:;
Sent: Friday, April 17, 2015 1:27 PM
To: CODE4LIB@LISTSERV.ND.EDU javascript:;
Subject: [CODE4LIB] Modeling a repository's objects in a relational
database
Hullo.
I'm interested to hear about people's approaches for modeling
repository objects in a normalized, spec
:; on
behalf of Stephen Schor stephensc...@nypl.org javascript:;
Sent: Friday, April 17, 2015 1:27 PM
To: CODE4LIB@LISTSERV.ND.EDU javascript:;
Subject: [CODE4LIB] Modeling a repository's objects in a relational
database
Hullo.
I'm interested to hear about people's approaches
