Sort issues by unit in the document detailed view #1437
Assignees
Labels
Comments
6 tasks
|
Fixed in rero/rero-ils-ui#425 |
BadrAly
pushed a commit
to BadrAly/rero-ils
that referenced
this issue
Nov 12, 2020
Adds a daily job to: 1. Change the issue status to LATE for all expected issues when the expected date is passed. 2. Change the issue status to CLAIMED for LATE issues when the corresponding holdings record has a valid vendor with an email address and max_number_of_claims is not reached. 2.1. Change the issue status to CLAIMED for all LATE issues when the days_for_first_claim is passed. 2.2. Increment the claims_count field for all CLAIMED issue if the days_for_next_claim passed. The job is scheduled to run every midnight. * Improves inheritance between the Item, ItemIssue classes. * Closes rero#1437 * Closes rero#1435 * Create tests and fixtures accordingly. Co-Authored-by: Aly Badr <[email protected]>
BadrAly
pushed a commit
that referenced
this issue
Nov 12, 2020
Adds a daily job to: 1. Change the issue status to LATE for all expected issues when the expected date is passed. 2. Change the issue status to CLAIMED for LATE issues when the corresponding holdings record has a valid vendor with an email address and max_number_of_claims is not reached. 2.1. Change the issue status to CLAIMED for all LATE issues when the days_for_first_claim is passed. 2.2. Increment the claims_count field for all CLAIMED issue if the days_for_next_claim passed. The job is scheduled to run every midnight. * Improves inheritance between the Item, ItemIssue classes. * Closes #1437 * Closes #1435 * Create tests and fixtures accordingly. Co-Authored-by: Aly Badr <[email protected]>
BadrAly
pushed a commit
that referenced
this issue
Nov 12, 2020
Adds a daily job to: 1. Change the issue status to LATE for all expected issues when the expected date is passed. 2. Change the issue status to CLAIMED for LATE issues when the corresponding holdings record has a valid vendor with an email address and max_number_of_claims is not reached. 2.1. Change the issue status to CLAIMED for all LATE issues when the days_for_first_claim is passed. 2.2. Increment the claims_count field for all CLAIMED issue if the days_for_next_claim passed. The job is scheduled to run every midnight. * Improves inheritance between the Item, ItemIssue classes. * Closes #1437 * Closes #1435 * Create tests and fixtures accordingly. Co-Authored-by: Aly Badr <[email protected]>
iGormilhit
pushed a commit
that referenced
this issue
Nov 12, 2020
Adds a daily job to: 1. Change the issue status to LATE for all expected issues when the expected date is passed. 2. Change the issue status to CLAIMED for LATE issues when the corresponding holdings record has a valid vendor with an email address and max_number_of_claims is not reached. 2.1. Change the issue status to CLAIMED for all LATE issues when the days_for_first_claim is passed. 2.2. Increment the claims_count field for all CLAIMED issue if the days_for_next_claim passed. The job is scheduled to run every midnight. * Improves inheritance between the Item, ItemIssue classes. * Closes #1437 * Closes #1435 * Create tests and fixtures accordingly. Co-Authored-by: Aly Badr <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Public interface: For the screens where the items are displayed (holdings and document detail screens)
show only received issues in the document detailed view. Ideally sort issues by unit (decreasing).
The text was updated successfully, but these errors were encountered: