125 lines
2.3 KiB
Plaintext
125 lines
2.3 KiB
Plaintext
|
head 1.6;
|
||
|
|
access;
|
||
|
|
symbols;
|
||
|
|
locks; strict;
|
||
|
|
comment @# @;
|
||
|
|
|
||
|
|
|
||
|
|
1.6
|
||
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.5;
|
||
|
|
|
||
|
|
1.5
|
||
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.4;
|
||
|
|
|
||
|
|
1.4
|
||
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.3;
|
||
|
|
|
||
|
|
1.3
|
||
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.2;
|
||
|
|
|
||
|
|
1.2
|
||
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.1;
|
||
|
|
|
||
|
|
1.1
|
||
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
||
|
|
branches;
|
||
|
|
next ;
|
||
|
|
|
||
|
|
|
||
|
|
desc
|
||
|
|
@Initial revision
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.6
|
||
|
|
log
|
||
|
|
@Revision 6
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@---+ Count Request Type
|
||
|
|
|
||
|
|
This request only returns the number of:
|
||
|
|
a. records for seaches
|
||
|
|
* distinct values for scans
|
||
|
|
|
||
|
|
In DiGIR & BioCASE sofar this has been implemented as an additional flag that can be set to true.
|
||
|
|
It would be worthwile considering it to be a seperate request method, as the returned data is very different. Consequently the two different count requests ( see above) should become two seperate methods.
|
||
|
|
|
||
|
|
---+++++ Proposed CountRequest
|
||
|
|
|
||
|
|
Although requesting a count returns a very different parameter than a search or a scan, we concluded that it is not necessary to have a seperate operation for this.
|
||
|
|
|
||
|
|
The approach taken ba DiGIR to include a count-flag with a SearchRequest or InventoryRequest could be used here as well. The count-flag works independend from the search/inventory response and turns on or off the counting of all matched records (search) or distinct values (inventory). The searhc or inventory would still return the desired records no matter what value the count-flag has. But if you request 0 records for a search or scan, than only the count should be returned. This is what was expected fro a seperate count request.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.5
|
||
|
|
log
|
||
|
|
@Revision 5
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d12 3
|
||
|
|
a14 1
|
||
|
|
to be completed
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.4
|
||
|
|
log
|
||
|
|
@Revision 4
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d1 1
|
||
|
|
a1 1
|
||
|
|
---+++ Count Request Type
|
||
|
|
d7 2
|
||
|
|
a8 2
|
||
|
|
In DiGIR & BioCASE sofar this is implemented as an additional flag that can be set to true.
|
||
|
|
It would be worthwile considering it to be another [[:../:][request method]]
|
||
|
|
d10 3
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.3
|
||
|
|
log
|
||
|
|
@Revision 3
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d4 1
|
||
|
|
a4 1
|
||
|
|
*.a records for seaches
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.2
|
||
|
|
log
|
||
|
|
@Revision 2
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d4 2
|
||
|
|
a5 2
|
||
|
|
a) records for seaches
|
||
|
|
b) distinct values for scans
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.1
|
||
|
|
log
|
||
|
|
@Initial revision
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d7 1
|
||
|
|
a7 1
|
||
|
|
in DiGIR & BioCASE sofar this is implemented as an additional flag that can be set to true.
|
||
|
|
@
|