Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

i729 Adjust logic determining if an Asset is missing children #730

Merged
merged 1 commit into from
Jul 20, 2023

Conversation

bkiahstroud
Copy link
Collaborator

Using "less than" instead of "does not equal" fixes a couple issues:

  • If a new child record was created through the UI, the Asset would be marked as missing children
  • If a pre-existing Asset, whose :intended_children_count had not been set, was updated outside of Bulkrax, it would be marked as missing children

Using "less than" instead of "does not equal" fixes a couple issues:
- If a new child record was created through the UI, the Asset would be marked as missing children
- If a pre-existing Asset, whose :intended_children_count had not been set, was updated outside of Bulkrax, it would be marked as missing children
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants