Customize Item-Level Record Display

[abelpink]

Item-level records in DSpace ("simple item view") display only certain metadata fields using DSpace-standard labels (see an example item record here). We'd like to customize the metadata fields that appear on the item-level page, as well as their labels.

The image below is a mockup of the UI for an item level record. I'm not sure what all is possible here in terms of layout, but hopefully this will at least gives you an idea of the labels and metadata that should be visible on this page. The numbered items' corresponding dublin core fields are mapped in the attached spreadsheet. Let me know if you have any questions!

Label_Element_Mapping.xlsx

[aseyedia]

Great, thanks for letting me know! I just spoke to Alex and he made me aware of the PCORnet AWS DSpace build as well. I'm assuming these instructions apply for both but I was just linking it in here in case you needed to know.

[aseyedia]

The "Simple Item View" has been (mostly) completed to match the above specifications.

Number on Image	Dublin Core Element Name	New Label (if applicable)	Complete?
1	type		✅
2	dc.title		✅
3	date.created	Created	✅
4	date	Last Modified	✅
5	subject.other	Tags	✅
6	description.abstract	Abstract	✅
7	contributor.author	Creator	✅
8	contributor.advisor	Reviewer	✅
9	contributor.other	Affiliations	✅
10	description.provenance[0]	Provenance	✅
11	description[0]	Description	✅
12	description[1]	Cohort Description	✅
13	relation.uri	Development Code	✅
14	subject	Vocabularies	✅
15	subject.mesh	Clinical Subject	✅
16	relation	Related Items	⛔️
17	relation.isreferencedby	Related Publications	⛔️
18	rights		✅
19	identifier.citation	Cite this Resource	⛔️
20	dc.description.version	Versioning	⛔️

Components related to relations and versions are, for the time being, unclear, because entities have not been yet configured (for relations) and most items do not have multiple versions. These elements should render dynamically once our database reaches that level of sophistication, but should we encounter problems, I will reopen this issue.