Add Resource Collection name to export package metadata #3783
Description
Feature Description
We are working to preserve the Manifold export packages and noticed the Resource Collection information is missing from the metadata. We don't require it, but if it is added e.g. to the resource-level metadata.json, we can retain this grouping of the resources in the preserved copy.
Why is this feature important? Who does it help?
It allows the ability to organize Resources into Collections to be retained when data is moved to another repository via export e.g. for preservation.
User Stories
As a preservation archive I'd like the metadata to include the Resource Collection name so that resources can be organized in a way that more closely reflects how they were displayed on the original website.
Design Notes
N/A
Development Notes
N/A