-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add datasets counts to publishers page #68
Comments
@alexiscott This ticket has replaced #427. Can you estimate it please? |
@rhabbachi Not quite there with this for Marine Scotland, but almost. I will send a message once this is ready. Thanks! |
From Alex on March 28th: "Hi @rhabbachi, just a heads up that I have added a PR for Marine Scotland (which should be easier for other sites - I added a description for that to the PR.) for ticket #68 here: |
Looks goods for marine scotland. @alexiscott do we need to do anything for the 2.x implementation? |
Yes, work still needs to happen for 2.0. I know that @dgading had some thoughts on this and the approach for data in 2.0 is cross app and will work differently. |
@alexiscott @dgading Should we just create a new ticket for the 2.0 implementation or should we keep that in this ticket? |
Moved to the backlog because we need to check with Alex if the 2.0 implementation aspect of this ticket needs to be tracked in the Support or in the Product board. |
User Story
When I go to the publisher page, I want to see how many datasets are available from each publisher, so that I know how much information I can expect to find from them.
Background
This is currently available on DKAN1, and we found in user testing that users accustomed to DKAN1 miss this feature.
Acceptance Criteria
When I go to the publisher page
Then I see the number of datasets for each publisher on that page
Working downstream on Marine Scotland /groups
Working upstream (8.x branch) on /publishers
Working upstream to 2.0
Estimate: 8
PR
GetDKAN/data-catalog-components#140
The text was updated successfully, but these errors were encountered: