search

hbz / mabxml-elasticsearch

Raw hbz union catalog data exposed via a web API
http://lobid.org/hbz01
3 stars 1 forks source link

Remove OAI-PMH elements from responses #48

Closed fsteeg closed 6 years ago

fsteeg commented 6 years ago

Originally our hbz01 URLs serving mabxml were only intended for internal debugging, so we simply took our export data as it was and exposed it. But actually the OAI-PMH elements (OAI-PMH, ListRecords etc.) make no sense in the context of single resources like http://lobid.org/hbz01/HT000052997

I think we should only serve the OAI-PMH / ListRecords / record / metadata / record element.

I suggest that we clean this up after announcing it on the list with some time for people to adapt.

dr0i commented 6 years ago

The OAI-PMH elements make indeed no sense. ExLibris did this all wrong. But: if you change the structural consistence now most (all?) processing programs trained on the bad original structure will break. @fsteeg is there any real need to change the structure?

fsteeg commented 6 years ago

There is no rush, so we could announce it with some generous time (6 months?), but I think we should fix this at some point.

fsteeg commented 6 years ago

We could implement the new format as a route under resources (like we do for deletions), so something like resources/hbz01/ (or some other name if that makes sense, like resources/mabxml/) and leave the current format running for a while.

dr0i commented 6 years ago

Again, I advice against it. It's the original "aleph MAB XML", used by others e.g. in Austrian, and no need to invent another structure and break any process routine. Also, Aleph is going to be replaced, thus Aleph-Mab-Xml.

acka47 commented 6 years ago

Let's discuss this on a Thursday when everybody is in the office.

fsteeg commented 6 years ago

We decided to leave it as it is, for consistency with published dumps and simplicity. Closing.