Dataverse having problems consuming API

cessda-bitbucket-importer commented 4 years ago

Original report on BitBucket by John Shepherdson (GitHub: john-shepherdson).

From: Vyacheslav Tykhonov

Subject: Re: CVS + Code Quality

Date: 28 February 2020 at 14:26:02 CET

To: Carsten Thiel >

Hi Carsten,
Just for your information: we’re testing the connection of the latest Dataverse version to CESSDA Controlled Vocabularies and discovered problems with landing pages of terms. For example, try thishttps://vocabularies.cessda.eu/TopicClassification#SocialStratificationAndGroupings.FamilyLifeAndMarriage/2.0
Another thing I don’t quite understand why the same term appears in results a few time for the different versions of the same vocabulary, it’s a bit odd (please see screenshot).
Best,Slava
<Screen Shot 2020-02-27 at 7.28.48 PM.png>
Best,Slava

On Feb 4, 2020, at 10:55 AM, Carsten Thiel wrote:
Yes, it's production.

I'm CCing John who is in contact with them on SQA Baseline. They were discussing CDC, which is not restricted.

On 4 Feb 2020, at 10:51, Vyacheslav Tykhonov wrote:

Great, is it in production already? URL will not change?

And the other question - we're working on SQA baseline in EOSC Synergy and they're investigating CESDA Maturity Model. Guys told me that they've got from CESDA access to some data repository in the restricted bitbucket, is it Dataverse or something else?

Cheers,
Slava

‌

cessda-bitbucket-importer commented 4 years ago

Original comment by John Shepherdson (GitHub: john-shepherdson).

On Mar 4, 2020, at 7:42 AM, Nugraha, Sigit wrote:

Hi Carsten,
Sorry, I was sick for around 10 days, now back to work again.
Ok, I need more detailed information about this issue.How the vocabularies are fetched from CVS?Is it retrieved from the API or from the page https://vocabularies.cessda.eu/#!detail/TopicClassification?
I will try to find a solution after I have more detailed information. However, I am not sure if I have time this week, due to the deadline on the other projects.And next week I will be on vacation.
Actually, I have developed some new sets of APIs and interface for CVS publication side, which is more faster and reliable,which should be ready by this month.
Thank you.

Best Regards,Sigit

‌

cessda-bitbucket-importer commented 4 years ago

Original comment by John Shepherdson (GitHub: john-shepherdson).

Nugraha, Sigit

4 March 2020 at 08:15

To: Carsten Thiel , Vyacheslav Tykhonov

Cc: Taina Jääskeläinen (TAU), John Shepherdson

Hi,

Yes, the old APIs endpoints "/v1" will not be changed. I will only add more "/v1" APIs related to search and file downloads on specific formats.

For the currently available APIs, please take a look here https://vocabularies.cessda.eu/swagger-ui.html

@‌Slava

Sorry actually, I am unable to resolve this URL in CVS.

https://vocabularies.cessda.eu/TopicClassification#SocialStratificationAndGroupings.FamilyLifeAndMarriage/2.0. I got 404-page-not-found. Therefore, it is still not clear for me about the source of the Vocabularies dataset.

Currently, the CVS URL page always has "#!" in the URL, due to the framework used for developing the tool.

e.g. https://vocabularies.cessda.eu/#!detail/TopicClassification

And the APIs URL always has "/v1" or "/v2" on the URL

e.g. https://vocabularies.cessda.eu/v1/vocabulary-details/TopicClassification/en/4.0

Thank you.

Best,

Sigit

cessda-bitbucket-importer commented 4 years ago

Original comment by John Shepherdson (GitHub: john-shepherdson).

‌

cessda-bitbucket-importer commented 4 years ago

Original comment by sigit nugraha.

This will be checked after the API documentation in CVS2 is done.
Hopefully by the ready by the end of this week/next week.

cessda-bitbucket-importer commented 3 years ago

Original comment by Taina Jääskeläinen.

This is good to get fixed as maybe the reason that the validator is currently allowing all versions of vocabularies in their validation which is not useful.

cessda-bitbucket-importer commented 3 years ago

Original comment by John Shepherdson (GitHub: john-shepherdson).

cessda / cessda.cvs.two

Dataverse having problems consuming API #178