Add pageCount to crawls and uploads and use in frontend for page counts #2315
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2257
This is a follow-up to the public collections work, which adds pages to the database for uploads. All crawls and uploads now have a
pageCount
field which is populated when the item is successfully added. A new migration is also added to populate the field for existing archived items that don't have it set yet.OrgMetrics have also been modified to include
crawlPageCount
anduploadPageCount
, and to include the total of both inpageCount
, and all three included in the frontend org dashboard.The frontend has been updated to use
pageCount
rather thanstats.done
wherever appropriate, meaning that in archived item lists and details we now have a consistent page count for both crawls and uploads.Screenshots
Org Dashboard
Archived Items list
Crawl Detail
Upload Detail
Collection Archived Items List
Testing
(Requires having both backend and frontend deployed from this branch)
New functionality
Migration