12111
Reporter: lfrancke
Assignee: mdoering
Type: Bug
Summary: Registry WS does not show all tags
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-10-26 11:16:15.71
Updated: 2013-12-16 17:51:02.974
Resolved: 2012-10-26 22:49:45.353
Description: http://staging.gbif.org:8080/registry-ws/dataset/78ff18a6-1c32-11e2-af65-00145eb45e9a/tag vs. http://staging.gbif.org:8080/registry-ws/dataset/78ff18a6-1c32-11e2-af65-00145eb45e9a/
http://staging.gbif.org:8080/registry-ws/dataset/7c6b0450-1c32-11e2-af65-00145eb45e9a/ vs. http://staging.gbif.org:8080/registry-ws/dataset/7c6b0450-1c32-11e2-af65-00145eb45e9a/tag
Seem to just ignore _some_ namespaces? At least HIT.]]>
Author: mdoering@gbif.org
Created: 2012-10-26 13:30:13.397
Updated: 2012-10-26 13:47:30.251
The AgentSupport class adds readonly HIT tags using the extended properties and metadata tables in the back.
It feels we dont load any tags at all but just expose those readonly ones successfully. Investigating.
Author: kbraak@gbif.org
Comment: I believe we agreed not to eagerly load any tags in yesterday's discussion, right? Therefore, we will need to remove these HIT, and return them as part of /tags only.
Created: 2012-10-26 13:56:17.03
Updated: 2012-10-26 13:56:17.03
Author: mdoering@gbif.org
Created: 2012-10-26 14:00:06.157
Updated: 2012-10-26 14:09:07.719
well, we havent reached a final decision on eagerly loading. We need to revisit that with the new API.
For now I will make sure we eagerly load all tags - as the S-HIT is build on that assumption and we dont yet have so many tags.
... I wished we already started REG-259