Dear all,
If you ever created a REST API, you might run into the problem,
whether searching should be implemented via GET or POST methods. There
are lots of debate around this supported by different theoretical
considerations.
Maybe these debates will be ceased soon, because last week Julian
Colleagues,
Please pardon the cross-posting.
Best regards,
Ed
Edward Sanchez
Head, Library Information Technology
Marquette University
W: 414-288-6043
M or Text: 414-839-9569
Marquette University Raynor Memorial Libraries
Emerging Technologies Librarian
Reports to the Head of Library
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
Stephen,
As the lead developer on the SobekCM open-source digital repository project and
formerly a developer for the University of Florida Libraries, I have looked at
this quite a bit and learned a bit over time.
I began development working on tracking systems to manage a fairly large-scale
*** Please excuse cross-posting. ***
The 78th Annual Meeting of the Northern California Technical Processes
Group is fast approaching! We have a fantastic line-up
of speakers discussing this year's theme: Production, Distribution,
Access: Navigating the Confluence of Publishers, Vendors, and
Dear Colleagues,
We are pleased to announce that information on accepted paper, panel, and
24x7 sessions at Open Repositories 2015 is now available on the OR2015
conference website: http://www.or2015.net/
Open Repositories 2015, taking place in Indianapolis on June 8-11, received
an
A great idea, I think, but I would not bet on soon...
On Friday, April 17, 2015, Péter Király kirun...@gmail.com wrote:
Dear all,
If you ever created a REST API, you might run into the problem,
whether searching should be implemented via GET or POST methods. There
are lots of debate around
This is a beautiful response, and the payoff, at the end, is perfect... Try
it, you probably won't like it. In practice, even with big hardware,
relational databases get mired down with MARC and MODS once the collection
size becomes significant..
Cary
On Friday, April 17, 2015, Mark V. Sullivan
You might consider a NoSQL database, either memory (redis, etc.) or disk based
(MongoDB, etc.) depending on your needs. There are also triple-store specific
DBs like SparkleDB.
Cary
On Apr 17, 2015, at 5:01 PM, Stephen Schor stephensc...@nypl.org wrote:
Firstly - thanks for the thoughtful
Firstly - thanks for the thoughtful replies, links, and anecdotes.
We end up storing a lot of MODS as text in a database.
We map it out as other formats...but our app deals in *a lot* of mods.
A lot of time and line-count is dedicated to turning XML into an
object/datastructure
that can be sent
12 matches
Mail list logo
