the database function asset.staff_ou_record_copy_count was using the hardcoded status list of (0,7,12) to count "available" copies instead of obtaining a list of config.copy_status where is_available is true.
if this change is acceptable, other database functions that include the hardcoded (0,7,12) list may want to be updated as well:
* asset.staff_lasso_record_copy_count
* asset.staff_ou_metarecord_copy_count
* asset.staff_lasso_metarecord_copy_count
the database function asset.staff_ ou_record_ copy_count was using the hardcoded status list of (0,7,12) to count "available" copies instead of obtaining a list of config.copy_status where is_available is true.
here's a branch where the asset.staff_ ou_record_ copy_count function uses the same logic as asset.opac_ ou_record_ copy_count: http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ abellenir/ lp1775216- inconsistent- avail-counts
if this change is acceptable, other database functions that include the hardcoded (0,7,12) list may want to be updated as well: lasso_record_ copy_count ou_metarecord_ copy_count lasso_metarecor d_copy_ count
* asset.staff_
* asset.staff_
* asset.staff_