Keith Chapman wrote:
Chathura C. Ekanayake wrote:
Below are the features/changes/fixes need to be done in the 1.0 release
of the Registry (as we discussed in today's meetings with Dr. Sanjiva,
Paul, Glen and Jonathan).
Core Registry
==========
* Add import method to the Registry interface to import resources using
URLs.
* Split the Registry interface to a MinimalRegistry and Registry
* Add "boolean tagExists(String resourcePath, String tag)" to the
Registry interface (this is requested by the Mashup team)
Well Glen's suggestion was that this is not needed and that a resource
can be tagged multiple times with the same tag. The bug is really that
the registry throws an exception when this is attempted. Glen and
Jonathan might have more details on this.
A resource can be tagged with the same tag by multiple users. But IMHO
we shouldn't allow the *same user* to tag a resource multiple times with
the same tag. It breaks some concepts of taggings. We use tag count
(number of taggings done on a resource using a tag) as a method to
determine the relevance of a tag to a resource. We highlight the tags in
the tag cloud according to the tag count. If we allow the above
scenario, a user can tag his resource with the same tag multiple times
and artificially increase the tag count of that resource. This could
mislead other users about the relevance of that tag on that resource.
Thanks,
Chathura
Thanks,
Keith.
* Registry interface method to search resource by media type.
* Change put(...) method to take the suggested path and return the
actual path.
* Implement resource renaming (This may take lot of time and may extend
beyond the 11th deadline)
* Fix resource put protocol in APP. Use HEAD to check whether the
resource exists. Then use POST if resource does not exist. Use PUT if
the resource already exists.
* Fix some minor protocol issues in the APP interface to match with the
protocol defined in the wiki.
Web UI
======
* Functionality for browsing, adding and editing properties of resources
* Provide tagging box with add resource / add collection UIs
* Make the resource name and media type fields disabled. And provide
buttons next to them to edit them.
* UI for searching resources by media type
* Auto complete for taggings - optional
In addition to above we have 73 open JIRAs to resolve (many of them are
trivial, but some may take lot of time). So I think we can follow below
plan for achieving our goal of releasing Registry 1.0 on 28th January.
9th to 11th - Complete all core Registry features (we have to allocate
time for meetings as well)
11th to 18th - Complete UI features + work on JIRAs
18th to 27th - QA + work on JIRAs
Please add any missing features or remove unnecessary features from
above lists.
Thanks,
Chathura
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
_______________________________________________
Registry-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
