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

Update for TNS 2.0 #39

Open
2 of 3 tasks
jchate6 opened this issue Jan 3, 2025 · 0 comments · May be fixed by #41
Open
2 of 3 tasks

Update for TNS 2.0 #39

jchate6 opened this issue Jan 3, 2025 · 0 comments · May be fixed by #41
Assignees
Labels
User Issue Raised by a user

Comments

@jchate6
Copy link
Contributor

jchate6 commented Jan 3, 2025

We need to make sure that TNS v2.0 changes haven't affected current TOM_TNS, and also update tom_TNS to work with TNS v2.0.

From TNS:

Please note that there is a change that has to be performed on your side for continuing to submit reports via the API. 

(We've added a clarification to the released NewsFeed.)

In order to submit reports you must add /set/ to the URL:
https://www.wis-tns.org/api/set/bulk-report

The reply is obtained with /get/ in the URL:

https://www.wis-tns.org/api/get/bulk-report-reply 

Note that the file-upload and prop-period are called with set: /api/set/file-upload, /api/set/prop-period
whereas the Search and Get objects APIs are called with get: api/get/search, api/get/object
All these are specified in the updated manuals, available from the help page.

Sorry for having missed this clarification earlier, and thanks for your understanding.

Best regards,

The TNS team.

Tasks:

  • Remove 'reply layer from Broker
  • Remove 'reply' layer from TNS Harvester
  • tom_TNS:
@jchate6 jchate6 moved this to Triage in TOM Toolkit Jan 3, 2025
@jchate6 jchate6 added the User Issue Raised by a user label Jan 10, 2025
@jchate6 jchate6 moved this from Triage to In progress in TOM Toolkit Jan 10, 2025
@jnation3406 jnation3406 linked a pull request Jan 17, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
User Issue Raised by a user
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

2 participants