=====================================
Web Interface to the Registry: Issues
=====================================


Search Form
-----------

* More keys could be added to the modified "Detail Value" search (if our
  query is something like detail_value ILIKE '%value%', it doesn't make
  sense to query on number-like values).

* We should probably expose the Offset form field (but unobstrusively).

* Let people select what relationships to look for?  You'd have to
  change the operator-related-to template and probably have a
  specialized condition maker, too.

* Our handling of relationships currently sucks.  The least we should
  do is display the relationship type in the result display -- but
  frankly, that's still not what I'd like to see.  Hm.

* Due to the 1:n relation between "rr.resource" and "rr.capability", and
  another 1:n relation between "rr.capability" and "rr.relationship",
  we get identical elements in our "array_agg(standard_id)" array.

Content
-------

* I'm *quite* sure we want to SAMP-send the whole match (rather than
  what happens to be visible due to paging).  Figure out how that works
  -- could the client fetch the resource list directly from the DC
  server?

Docs
----

* The UCD thing must be documented in some way (plus: maybe let people
  use the UCD resolver to come up with them).

* We need developer docs (what's what?  what do I have to do if?...) in 
  README (or somewhere else).

Style
-----

* (defer to when we do a solid refactoring): There should be javascript
  object alongside the form, keeping stuff like maxrec, offset, and
  probably the conditions themselves, outside of the DOM.

* fetchContactInfo should check data[status] and give some meaningful
  error indication if the query failed.

* We need solid metadata in the RD (this may be one for Markus).