NACTEM should release their tools as installable packages, then they can be integrated more easily into repositories, rather than the less scalable SOA. If you're ingesting large amounts of data, you can't expect to send it all to a web service for processing.
(And of course a plug for Cheshire3, which does all this already)
Putting hooks into eprints is pretty easy but I would not want to send the document to a web service while the depositing user waited, but it's very easy to trigger events when the item is added (we auto twitter each time something is added!)
Sounds to me like something which would be processed in a background script to add value to records?
Good work, Brian ;)
NACTEM should release their tools as installable packages, then they can be integrated more easily into repositories, rather than the less scalable SOA. If you're ingesting large amounts of data, you can't expect to send it all to a web service for processing.
(And of course a plug for Cheshire3, which does all this already)
azaroth41 2 years ago
Putting hooks into eprints is pretty easy but I would not want to send the document to a web service while the depositing user waited, but it's very easy to trigger events when the item is added (we auto twitter each time something is added!)
Sounds to me like something which would be processed in a background script to add value to records?
eprints 2 years ago