Feature #728

Updated by Matthieu Decorde about 5 years ago

The portal should be able to expose itself to OAI harvesters.
This supposes unique identifiers for corpus texts.

Solution 1:
The OAI identifiers can match static portal URLs served by servlet container (Tomcat).
ex: http://catalog.bfm-corpus.org/qgraal_cm

Solution 2:
The OAI identifiers can match dynamic URLs served by TXM portal
ex: http://txm.bfm-corpus.org/?command=record&corpus=BFM&textid=qgraal_cm

h2. State of the art harvesters

Existing servlet implementations :
http://www.oclc.org/research/activities/oaicat.html?urlm=159694
http://www.dlese.org/oai/

Back