You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see, it is aDiscoverySearchFilterFacet that I've placed in the sidebarFacets section of my defaultConfiguration. The behavior I would like is to create a sidebar facet that lists like maybe 5-10 of the highest-hitting Project entries related to Concept Sets, and then the rest are like "load more" or something like that.
However, what is happening is this:
Instead of the dc.title of the Project (this is a customization of the default Project), we are given the UUID of this Project. I understand that Project is distinct from Publication, but we have created a number of Publication-like Entity Types for this instance of DSpace and Project is intended to be one of them; I also had to alter ds-project-search-result-list-element to show dc.description in a Search List because by default, it showed nothing.
Describe the solution you'd like
Like I mentioned before, I would like a list of maybe hyperlinked dc.titles of these Project entries, allowing the user to subset by related Project Item. The functionality is almost there, I just want the UUID to be rendered.
Describe alternatives or workarounds you've considered
Based on an investigation of the DOM, it seems that the lowest-level Angular component that governs the behavior of these little boxes is ds-search-facet-option.
However, exactly how I would go about rendering the UUID is beyond me. I have tried getting the DSO for the UUID using functions dso-redirect.service.ts and then later identifiable-data.service.ts and then extracting the name using dsoNameService.getName(dso), but that doesn't seem to be working.
Additional information
If I could get a pointer in the right direction, I would be happy to try to implement this myself, because as it stands, I'm concerned that I'm too narrowly focused on ds-search-facet-option.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In our custom DSpace configuration, I have a relationship in
discovery.xml
calledisProjectOfConceptSet
:As you can see, it is a
DiscoverySearchFilterFacet
that I've placed in thesidebarFacets
section of mydefaultConfiguration
. The behavior I would like is to create a sidebar facet that lists like maybe 5-10 of the highest-hitting Project entries related to Concept Sets, and then the rest are like "load more" or something like that.However, what is happening is this:
Instead of the
dc.title
of the Project (this is a customization of the default Project), we are given the UUID of this Project. I understand that Project is distinct from Publication, but we have created a number of Publication-like Entity Types for this instance of DSpace and Project is intended to be one of them; I also had to alterds-project-search-result-list-element
to showdc.description
in a Search List because by default, it showed nothing.Describe the solution you'd like
Like I mentioned before, I would like a list of maybe hyperlinked
dc.title
s of these Project entries, allowing the user to subset by related Project Item. The functionality is almost there, I just want the UUID to be rendered.Describe alternatives or workarounds you've considered
Based on an investigation of the DOM, it seems that the lowest-level Angular component that governs the behavior of these little boxes is
ds-search-facet-option
.However, exactly how I would go about rendering the UUID is beyond me. I have tried getting the DSO for the UUID using functions
dso-redirect.service.ts
and then lateridentifiable-data.service.ts
and then extracting the name usingdsoNameService.getName(dso)
, but that doesn't seem to be working.Additional information
If I could get a pointer in the right direction, I would be happy to try to implement this myself, because as it stands, I'm concerned that I'm too narrowly focused on
ds-search-facet-option
.The text was updated successfully, but these errors were encountered: