registry-ws: dataset/<key>/tag returns empty array when tags exist for dataset
11943
Reporter: kbraak
Assignee: jcuadra
Type: Bug
Summary: registry-ws: dataset/<key>/tag returns empty array when tags exist for dataset
Priority: Critical
Resolution: WontFix
Status: Closed
Created: 2012-09-24 18:16:54.685
Updated: 2013-12-16 17:50:16.935
Resolved: 2013-02-15 16:52:37.86
Description: http://b3g4.gbif.org:8080/registry-ws/dataset/856734ce-f762-11e1-a439-00145eb45e9a/tag should return an array of tags.
Looking at http://b3g4.gbif.org:8080/registry-ws/dataset/856734ce-f762-11e1-a439-00145eb45e9a confirms the dataset has tags.
According to the API ( http://dev.gbif.org/wiki/display/POR/Webservice+API ) this should be possible. Already, we can successfully return:
Identifiers:
http://b3g4.gbif.org:8080/registry-ws/dataset/856734ce-f762-11e1-a439-00145eb45e9a/identifier
Contacts:
http://b3g4.gbif.org:8080/registry-ws/dataset/856734ce-f762-11e1-a439-00145eb45e9a/contact
Endpoints:
http://b3g4.gbif.org:8080/registry-ws/dataset/856734ce-f762-11e1-a439-00145eb45e9a/endpoint
Please note, the SuperHIT just grabs the tags from the /dataset/key JSON response
]]>
Author: mdoering@gbif.org
Created: 2012-09-25 12:20:45.541
Updated: 2012-09-25 12:21:15.57
I wonder if we really intended to return all tags in the dataset response. I would have thought we only include public tags there and ignore all tags with a namespace.
The tag subresource should definitely have all tags for all NS - any only filter them if a ns=XYZ query parameter was supplied
Author: jcuadra@gbif.org
Created: 2013-02-15 16:52:32.474
Updated: 2013-02-15 16:52:32.474
This issue has been fixed in REG-336
Working examples:
http://api.gbif.org/uat/dataset/856734ce-f762-11e1-a439-00145eb45e9a/tag
http://api.gbif.org/uat/dataset/856734ce-f762-11e1-a439-00145eb45e9a/identifier
http://api.gbif.org/uat/dataset/856734ce-f762-11e1-a439-00145eb45e9a/contact
http://api.gbif.org/uat/dataset/856734ce-f762-11e1-a439-00145eb45e9a/endpoint