The-Academic-Observatory / oaebu-workflows

Telescopes, Workflows and Data Services for the 'Book Analytics Dashboard Project (2022-2025)', building upon the project 'Developing a Pilot Data Trust for Open Access eBook Usage (2020-2022)'
https://documentation.book-analytics.org/
Apache License 2.0
5 stars 0 forks source link

Telescope workflow implementation: Ebsco #6

Closed aroelo closed 1 year ago

aroelo commented 4 years ago
aroelo commented 3 years ago

@alkimozaygen Could you have a look at the questions in the description of this issue?

alkimozaygen commented 3 years ago

@aroelo

I will try to learn about your other questions and let you know.

alkimozaygen commented 3 years ago

@Aniek I forwarded your questions to the University of Michigan Press. Below are Charles Watkinson's answers.

rhosking commented 3 years ago

Thanks Alkim. It sounds like for this to be a viable option for developing a telescope, we need a better understanding of what those internal processes are. Might it be an option, possibly via Charles, to ask EBESCO what options they have for providing something more routine and consistent? and ideally directly from EBESCO to our account

aroelo commented 3 years ago

Thanks for those quick answers @alkimozaygen . I agree with @rhosking it would be really helpful if we could get something more automatically generated.

We could possibly work around the fact that the email is not send automatically by manually checking the mail ourselves, downloading the report and putting it on the SFTP server.

This would still leave an issue though if the report itself is not generated automatically either. The most concerning I think would be that one of the fields is only available in the January report. If this is a sign that fields randomly may or may not be in the report, it will be hard to work with the data.