Amen, it's good you're building tools around these standards. It'd be nice to factor out the code that fetches the data from the code that builds the index in the next iteration! ________________________________ From: Code for Libraries <CODE4LIB@LISTS.CLIR.ORG> on behalf of Eric Lease Morgan <emor...@nd.edu> Sent: Tuesday, October 29, 2019 8:25 AM To: CODE4LIB@LISTS.CLIR.ORG <CODE4LIB@LISTS.CLIR.ORG> Subject: Re: [CODE4LIB] ojs api [resolved]
> Sounds good! Well, not really. It wasn't until a day later that I learned OJS supports OAI, and in the past couple of days I hacked something to use OAI to do the same thing --> https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fericleasemorgan%2Findex-ital&data=02%7C01%7Cdouglas.duhaime%40yale.edu%7C5b0be035ad1649420cf008d75c6b2de3%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637079487731096361&sdata=76m%2BLX%2FNKtO7rj6QHvs5NBS4APCId28q3C5ob9BxLr8%3D&reserved=0 Using the OJS API was like scratching my left year by reaching around my head with my right arm. Using OAI is applicable to other repositories, and the OJS implementation of OAI both pretty good and wide-spread. --Eric M.
