I’m making a note of this here in case I need it again.
For a record in the Lincoln Repository with a given EPrints record ID (e.g. 4904), it’s possible to get the data behind the record in various formats, using the following URLs (N.B. how the record ID appears twice in each URL):
JSON
http://eprints.lincoln.ac.uk/cgi/export/4904/JSON/lirolem-eprint-4904.js
EPrints XML
http://eprints.lincoln.ac.uk/cgi/export/4904/XML/lirolem-eprint-4904.xml
BibTeX
http://eprints.lincoln.ac.uk/cgi/export/4904/BibTeX/lirolem-eprint-4904.txt
RefWorks tagged format
http://eprints.lincoln.ac.uk/cgi/export/4904/RefWorks/lirolem-eprint-4904.ref
HTML citation
http://eprints.lincoln.ac.uk/cgi/export/4904/HTML/lirolem-eprint-4904.html


Or even easier….
http://eprints.lincoln.ac.uk/4904/
right click, show source
It’s all in the link rel tags.
Of course!
Obviously that’s how Google etc. indexes the Repo pages… but is the existence of <meta> content in a page useful to developers? I.e. could I point Nick at the page and say “…it’s all in there, just view source”? Could he then build applications that use the data from just that?It’s a genuine question, I really don’t know.Edit: sorry, I see which bit of the HTML you’re talking about now. Yes, all of that data!!!