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

Display real Collection name, description and affiliation in the Collection Page #344

Closed
MellyGray opened this issue Mar 14, 2024 · 1 comment · Fixed by #352
Closed
Assignees
Labels
integration Tasks involving the connection and interaction of UI features with the Dataverse API pm.GREI-d-2.7.1 NIH, yr2, aim7, task1: R&D UI modules for creating datasets and supporting publishing workflows pm.GREI-d-2.7.2 NIH, yr2, aim7, task2: Implement UI modules for creating datasets and publishing workflows Size: 30 A percentage of a sprint. 21 hours. (formerly size:33) SPA: Collection Page UI Tasks related to the user interface (UI) or frontend development

Comments

@MellyGray
Copy link
Contributor

MellyGray commented Mar 14, 2024

Overview of the Feature Request

Display real Collection name, description, labels and affiliation in the Collection Page. Implement the UI logic and components to show this data and connect it to the js-dataverse use case.

This issue depends on:

Mock
image

What kind of user is the feature intended for?

This feature is intended for all users.

What inspired the request?

  • Suggestions from the beta proposal labeled as "nice to haves."

What existing behavior do you want changed?

None

Any brand new behavior do you want to add to Dataverse?

Add real Collection name, description, labels and affiliation in the Collection Page

Any open or closed issues related to this feature request?

@MellyGray MellyGray added pm.GREI-d-2.7.1 NIH, yr2, aim7, task1: R&D UI modules for creating datasets and supporting publishing workflows pm.GREI-d-2.7.2 NIH, yr2, aim7, task2: Implement UI modules for creating datasets and publishing workflows SPA: Collection Page Size: 30 A percentage of a sprint. 21 hours. (formerly size:33) labels Mar 14, 2024
@MellyGray MellyGray added UI Tasks related to the user interface (UI) or frontend development integration Tasks involving the connection and interaction of UI features with the Dataverse API Waiting labels Mar 14, 2024
@GPortas GPortas moved this to SPRINT READY in IQSS Dataverse Project Mar 14, 2024
@GPortas GPortas moved this from SPRINT READY to This Sprint 🏃‍♀️ 🏃 in IQSS Dataverse Project Mar 14, 2024
@MellyGray MellyGray moved this from This Sprint 🏃‍♀️ 🏃 to In Progress 💻 in IQSS Dataverse Project Mar 19, 2024
@MellyGray MellyGray removed the Waiting label Mar 19, 2024
@MellyGray MellyGray self-assigned this Mar 19, 2024
@MellyGray
Copy link
Contributor Author

Removing the Waiting tag because I already reviewed the js-dataverse PR and there are some changes requested, but the use case can already be used to retrieve the collection data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
integration Tasks involving the connection and interaction of UI features with the Dataverse API pm.GREI-d-2.7.1 NIH, yr2, aim7, task1: R&D UI modules for creating datasets and supporting publishing workflows pm.GREI-d-2.7.2 NIH, yr2, aim7, task2: Implement UI modules for creating datasets and publishing workflows Size: 30 A percentage of a sprint. 21 hours. (formerly size:33) SPA: Collection Page UI Tasks related to the user interface (UI) or frontend development
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant