Bug #1220
closedNeed systematic approach to viewing all data in database
0%
Description
This could be done with XML-XSL, but we would prefer give it a shot with
javabeans which are more efficient. Currently (Nov 21,2003) the metadata
viewing functions use the genericDispatcher to return beans, which are called
recursively throughout the page. We have had problems with the stability of
this approach. Better would be to have nested beans returned by one request.
This bug shall serve as a holding spot for any discussion on this, and should be
closed when the generic solution has been found and some parts of the database
viewable via this method. Then other bugs can be made to direct us as to what
exactly needs viewing.
Related issues
Updated by Michael Lee about 21 years ago
Making the 5 "major" bugs critical so that bugzilla highlights them in red, how
nice.
Updated by Michael Lee about 21 years ago
- Bug 847 has been marked as a duplicate of this bug. ***
Updated by P. Anderson over 20 years ago
Per the initial request, I'd say this bug can be closed. We have the
GenericDispatch action which works well, labeled as "Summary Report" on the plot
query results page. Improvements to the display are possible, but as stated
originally they should be new bugs.
Updated by Michael Lee over 20 years ago
Perhaps this bug is unclear. We need a way to view any data in the database by
simply calling a URL and perhaps a set of PK/AccessionCodes to view.
Something like:
vegbank.org/vegbank/view.do?accCode=VB.CC.123
and
vegbank.org/vegbank/view.do?tbl=party&PKs=1,4,14,56
--it wouldn't have to be as transparent as this, but this gives the idea.
We need to also think about the different views that these should produce and
name them. For example, summary view (standard spreadsheet view), comprehensive
view (field1: value1 <br/> field2: value2 <br/> etc.), PK translation (instead
of party_ID=45, we get "Jo Smith"), etc.
URLs add &view=summary
This is really important because as we accomplish new functionality, we want to
be able to see it. Right now, it's hard to really see what's going on in the db
if we make some nice change.
Updated by P. Anderson over 20 years ago
Apache's powerful URL rewriting capabilities gives us lots of options here. For one, I'd prefer to keep
the script name out of the URL entirely. e.g.
- View an entity by accession code in comprehensive (full) mode
http://vegbank.org/get/full/VB.CC.123
- View a list of parties by PK
http://vegbank.org/get/full/party/1,4,14,56
- Summary view
http://vegbank.org/get/summary/party/1,4,14,56
- Get raw XML for a given accession code
http://vegbank.org/get/xml/VB.CC.123
- Get raw XML for a given list of PKs
http://vegbank.org/get/xml/party/1,4,14,56
General form:
/get/ (AC | 'full' | 'summary' | 'xml') / (entity_name | AC)Something like that.
Updated by Michael Lee over 20 years ago
- Bug 1221 has been marked as a duplicate of this bug. ***
Updated by P. Anderson over 20 years ago
Squashing this bug with our first custom JSP tag, <vegbank:get> which uses
configurable SQL queries to populate a list or single bean or map in a JSP page.
First use was quite effective.
Updated by Michael Lee over 20 years ago
see http://gyro.nceas.ucsb.edu:8080/vegbank/forms/aux_role_viewall.jsp as an
example, created in 20 min by PMark and me