Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Date error in KBART records #95

Open
amandasramalho opened this issue May 15, 2017 · 3 comments
Open

Date error in KBART records #95

amandasramalho opened this issue May 15, 2017 · 3 comments

Comments

@amandasramalho
Copy link
Member

We have provided the links so that EBSCO could upload KBART records to EBSCO AtoZ. However, they have submitted the question below to, if possible, correct in our KBART:

While we are very glad to be able to have coverage and enumeration supplied in the KBART file, I wanted to point out some issues with incorrect coverage being provided in the hopes that it can be fixed going forward.

I have attached the KBART Journals file that we downloaded and also another file that shows the coverage that we currently have in the Knowledge Base (previously manually added, as coverage was not provided), the proposed change that the KBART file provides, and some examples of where this is not correct.

The trend that I am seeing is that for beginning coverage, if an issue has a range, it is bringing in the last month instead of the first month. For example, if a Journal’s beginning coverage is Jan-Feb 2015, Volume 42, and there are 4 issues, the correct beginning date would be Jan 2015, Volume 42, Issue 1. Instead, the KBART file is providing the LAST information in the range. In my example, the KBART file contains Feb 2015, Volume 42, Issue 4.

The data output is selecting the last month and the last issue instead of the first, as is customary with beginning coverage.

Also, there are end dates and enumeration missing in some cases.

Would you be able to look into this and see if there is a problem with the way the data is exported for the KBART file, or perhaps there is a reason it is being output this way?

I can also see that some of our current coverage definitely needs to be updated, but I wanted to reach out to you first to see if this might be a quick fix regarding the KBART file.

Thank you so much for your assistance.

Regards,
Jack Caddell

SCIELO KBART COVERAGE CHANGES 04212017.xls.zip

@amandasramalho
Copy link
Member Author

@gustavofonseca
Apenas um lembrete deste erro nos registros KBART.

@amandasramalho
Copy link
Member Author

Bom dia @gustavofonseca!
Apenas um lembrete deste erro nos registros KBART.

@gustavofonseca
Copy link

Ok @amandasramalho

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants