Digitisation Batch Throughput Items per Day Calculator
Track QC-accepted digitization throughput separately from capture count across actual productive-day exposure; no implied metadata completion or full preservation workflow completion.
Description
Captured items and QC-accepted items are separate production measures.
Captured items and QC-accepted items are separate production measures. Unequal productive-day exposure changes pooled throughput.
Track QC-accepted digitization throughput separately from capture count across actual productive-day exposure; no implied metadata completion or full preservation workflow completion.
When to use Digitisation Batch Throughput Items per Day Calculator
Use this tool to track QC-accepted digitization throughput separately from capture count across actual productive-day exposure; no implied metadata completion or full preservation workflow completion.
Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
How to use Digitisation Batch Throughput Items per Day Calculator and understand its results
- Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
- Enter capturedItemsPerBatch, rejectedItemsPerBatch, productiveBatchDays using the field table and calculation rules, then run the tool.
- Read acceptedItemsPerProductiveDayByBatch, pooledAcceptedItemsPerProductiveDay, pooledCaptureRejectionFraction. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| capturedItemsPerBatch | Captured items per batch | list of number | Required |
| rejectedItemsPerBatch | Rejected items per batch | list of number | Required |
| productiveBatchDays | Productive batch days | list of number | Required |
Align nonnegative integer captures and subset rejects with positive days; require positive total captures. Return local accepted rates, pooled accepted/total days and total rejection fraction.1
Paired lists must be nonempty and have equal lengths.
accepted/day = (captured − rejected)/productive days Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| acceptedItemsPerProductiveDayByBatch | Accepted items per productive day by batch | list of number |
| pooledAcceptedItemsPerProductiveDay | Pooled accepted items per productive day | number |
| pooledCaptureRejectionFraction | Pooled capture rejection fraction | number |
{
"input": {
"capturedItemsPerBatch": [
100,
200
],
"rejectedItemsPerBatch": [
10,
20
],
"productiveBatchDays": [
1,
3
]
},
"output": {
"acceptedItemsPerProductiveDayByBatch": [
90,
60
],
"pooledAcceptedItemsPerProductiveDay": 67.5,
"pooledCaptureRejectionFraction": 0.1
}
}Limitations and assumptions
QC acceptance does not establish metadata completion or a finished preservation workflow.
Numbers and computed results must be finite; overflow produces an error. Numeric lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Catalogue Record Completeness Field Counter: Audit caller-required catalogue fields across aligned records, distinguishing complete records from pooled field coverage; actual schema/presence criteria are caller established. For a complementary task, use Conservation Lab Annual Throughput Objects Estimate Calculator: Budget expected complete lab objects using caller productive hours and explicit complexity mix, not universal conservator-hour multipliers or a guaranteed integer mix allocation.
References
Similar or alternative tools
- Catalogue Record Completeness Field Counter
Audit caller-required catalogue fields across aligned records, distinguishing complete records from pooled field coverage; actual schema/presence criteria are caller established.
- Conservation Lab Annual Throughput Objects Estimate Calculator
Budget expected complete lab objects using caller productive hours and explicit complexity mix, not universal conservator-hour multipliers or a guaranteed integer mix allocation.