Shouldn't v1 shutdown be postponed?

shahoodshahood Member ✭✭

Hi @Simone @AmosDuveen @TaisFukushima

Since the release of v2, many issues in data have been posted, most of which are still unresolved. Following are those v2 related unresolved issues where comparison with v1 data is a must.

  1. https://forum.oxforddictionaries.com/api/discussion/267/v2-notes-are-sometimes-misplaced-within-results#latest

  2. https://forum.oxforddictionaries.com/api/discussion/242/v2-search-results-are-capped-at-500-or-489-instead-of-5000#latest

  3. https://forum.oxforddictionaries.com/api/discussion/220/why-does-search-endpoint-show-search-results-of-the-other-region#latest

  4. https://forum.oxforddictionaries.com/api/discussion/243/v2-senseids-are-not-appearing-in-sentences#latest

  5. https://forum.oxforddictionaries.com/api/discussion/239/v2-offers-lesser-examples-for-each-sense#latest

  6. https://forum.oxforddictionaries.com/api/discussion/241/differences-in-json-string-of-derivatives-v2-vs-v1#latest

In the light of above, shouldn't v1 shutdown be postponed till the time all such issues are resolved? If we lose access to v1, how would we be able to compare the results of both versions when the issue gets resolved?

Kindly look into this and reconsider your decision to shutdown v1 so early.

Thanks
Shahood

Tagged:

Answers

  • TaisFukushimaTaisFukushima Member, Administrator, Moderator admin

    Hello @shahood ,

    Thank you for bringing these to our attention, all bugs raised are being prioritised in our ongoing development. We can help with a few of the issues you have raised here as well.

    For the issues you’ve raised in points 4 & 5 these will be resolved in our next update v2.1 which we are aiming to release late July.

    Our API v2 is the biggest upgrade since 2016. Therefore, it is completely different from v1 in architecture, code, database, and data, so there are some changes in behaviour from v1, which you have outlined in points 3 & 6.

    As we continue to develop v2 we will continue to resolve bugs and issues and aim to make the API as valuable and usable as possible.

    Thanks again for your feedback.

Sign In or Register to comment.