search

project-lux / lux-frontend

Web front end of LUX
Apache License 2.0
3 stars 0 forks source link

Add events to sets (from 2038) #88

Open gigamorph opened 4 months ago

gigamorph commented 4 months ago

Problem Description: There is no way to connect the set to its event.

Expected Behavior/Solution: Add the missing data above. Connecting the set to its event will require a HAL link.

Requirements:

Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.

UAT/LUX Examples:

Dependencies/Blocks:

Related Github Issues:

Related links:

Wireframe/Mockup: Screenshot 2024-03-04 at 3 32 46 PM

roamye commented 2 months ago

@kkdavis14 to follow up with Rob to see if this is still good to do.

kkdavis14 commented 2 months ago

we can mark this low priority while Linked.art is sorting whether or not to do away with exhibition sets (needs community discussion).

updated: the exhibition HAL link can be low priority. other links between Sets > Groups could be added, as well as the Set classifications to the UI.

kkdavis14 commented 1 month ago

FYI @kamerynB @clarkepeterf Linked.art decided not to do away with Exhibition Sets. So this ticket can be worked on.

kamerynB commented 1 month ago

@kkdavis14 Thank you!

prowns commented 1 month ago

@kamerynB - can this be marked as unblocked?

kamerynB commented 1 month ago

@prowns I guess. I'll confirm with Kelly that the data is there and there isn't anything additional required on the backend.

Edit: The data is there.

prowns commented 1 month ago

Confirmed not blocked.

prowns commented 1 month ago

Ideally - the YCBA and YUAG sets would need to be merged in order to have an Exhibition set that can be used in this context. Without this, there is no SET page that a user would encounter.

Note - per Interactions, the separate links to YCBA exhibition set and YUAG exhibition set were removed from the right hand column since users could easily view all results and facet by repository.

agenda for data

clarkepeterf commented 1 week ago

@kamerynB @prowns @jffcamp do we want to add this to the next release because ML #186 and MT #40 are completed?

kamerynB commented 1 week ago

@clarkepeterf Added! Thank you!

roamye commented 12 hours ago

The original UAT link DNE. It exists in PROD, but when I search for the link through SS it does not show up under works. I am wondering if the original TST link: https://lux-front-tst.collections.yale.edu/view/set/664c4aeb-532f-46a2-9db8-4d0b51c73a64 is now: https://lux-front-tst.collections.yale.edu/view/text/83020c94-2797-4944-8044-6a6396e63b4c ... but this isn't a set...

if I put the original TST link into PROD the set record appears... but I also can't find this within the works simple searches in PROD or TST/DEV.

@kamerynB - would you be able to help find the original link? or is this a bigger issue that needs a BH?

prowns commented 11 hours ago

@roamye - tst is loading, so this should reappear.

prowns commented 11 hours ago

Also, this may be propose-close. Per comment above, we will not be offering links to unit-specific result sets from an exhibition. Users will view results for all objects in exhibition, and then use facets to refine by unit and/or collection.

@kkdavis14 or @azaroth42 - can you think of any use cases where this functionality will be necessary?

kkdavis14 commented 11 hours ago

I guess if they can't ever land on the Set, they don't need to get back to the Event from a Set

azaroth42 commented 11 hours ago

You can't search for them either -- they're really just a join table at this point. There could be other sets with events... but we can wait until that eventuates.

roamye commented 10 hours ago

@prowns - from your comment should this not be deployed then as it is proposed-closed?