Display of indexed metadata fields is currently limited. Numerous curators are requesting enhanced display: Reagan Murphy-Kao, Ray Hegemeier, Josh Schneider, Amy Hodge, Zhaohui Xue, Giovanni Svevo & more.
Arcadia Falcone is meeting with exhibit creators to obtain more specifics regarding this enhancement request. When specs/acceptance criteria are gathered, additional tickets will be created.
Related tickets, all Feature enhancement for metadata display:...
Display of indexed metadata fields is currently limited. Numerous curators are requesting enhanced display: Reagan Murphy-Kao, Ray Hegemeier, Josh Schneider, Amy Hodge, Zhaohui Xue, Giovanni Svevo & more.
Current Spotlight display is documented here: https://consul.stanford.edu/display/DIGMETADATA/MODS+indexing+and+display+in+SearchWorks+and+Spotlight#MODSindexinganddisplayinSearchWorksandSpotlight-B.SpotlightMODSdisplay(fromMODSindirectly,asindexedinSolr)
Arcadia Falcone is meeting with exhibit creators to obtain more specifics regarding this enhancement request. When specs/acceptance criteria are gathered, additional tickets will be created.
Related tickets, all Feature enhancement for metadata display:...
[ ] Index as series #384</p>
</li>
<li>
<p>[ ] Support active URL links in metadata display and narrative text #385 </p>
</li>
<li>
<p>[ ] Index end date of ranges #381 </p>
</li>
<li>
<p>[x] Index identifiers for display #383 </p>
</li>
<li>
<p>[ ] Don’t include <mods><genre> in topic index #382 </p>
</li>
<li>
<p>[ ] Index names separately by role (as well as collectively) #380 </p>
</li>
<li>
<p>[ ] Index notes separately by display label #379</p>
</li>
<li>
<p>[ ] Change criteria for author sort indexing #447</p>
</li>
</ul> </div>
</div>
<div class="comment">
<div class="user">
<a rel="noreferrer nofollow" target="_blank" href="https://github.com/caaster"><img src="https://avatars.githubusercontent.com/u/3210225?v=4" />caaster</a>
commented
<strong> 7 years ago</strong> </div>
<div class="markdown-body">
<p>Arcadia has met with several exhibit admins to gather information about their use cases & preferences. This information is preliminary, but provides an excellent window of info/understanding to exhibit admin needs. See attached spreadsheet.
<a href="https://github.com/sul-dlss/exhibits/files/559182/spotlight.user.interview.data.xlsx">spotlight user interview data.xlsx</a></p> </div>
</div>
<div class="comment">
<div class="user">
<a rel="noreferrer nofollow" target="_blank" href="https://github.com/arcadiafalcone"><img src="https://avatars.githubusercontent.com/u/7491842?v=4" />arcadiafalcone</a>
commented
<strong> 7 years ago</strong> </div>
<div class="markdown-body">
<p>Acceptance criteria matrix with more information about these issues.
<a href="https://github.com/sul-dlss/exhibits/files/717960/github_ticket_info_20170118.docx">github_ticket_info_20170118.docx</a></p> </div>
</div>
<div class="comment">
<div class="user">
<a rel="noreferrer nofollow" target="_blank" href="https://github.com/blalbrit"><img src="https://avatars.githubusercontent.com/u/796990?v=4" />blalbrit</a>
commented
<strong> 7 years ago</strong> </div>
<div class="markdown-body">
<p>@caaster @arcadiafalcone Parker will require the full suite of MODS fields that we would support in SW. It's hard to tell from this ticket - but how close are we to that now?</p> </div>
</div>
<div class="comment">
<div class="user">
<a rel="noreferrer nofollow" target="_blank" href="https://github.com/arcadiafalcone"><img src="https://avatars.githubusercontent.com/u/7491842?v=4" />arcadiafalcone</a>
commented
<strong> 7 years ago</strong> </div>
<div class="markdown-body">
<p>@blalbrit This documentation as to what is indexed in Spotlight is up to date (see table B): <a href="https://consul.stanford.edu/display/DIGMETADATA/MODS+indexing+and+display+in+SearchWorks+and+Spotlight">https://consul.stanford.edu/display/DIGMETADATA/MODS+indexing+and+display+in+SearchWorks+and+Spotlight</a></p>
<p>The short version is that SW iterates through most available MODS fields for display rather than using Solr indexes as Spotlight does, so Spotlight metadata display is significantly more limited, especially in terms of a) repeated fields (usually only the first instance is indexed) and b) attributes like displayLabel and type (only certain attributes, or their absence, result in the field being indexed). I can do a more detailed rundown of what is currently not available in Spotlight if that would be helpful. (It's on my list of things to do anyway, at request of exhibit owners.)</p> </div>
</div>
<div class="comment">
<div class="user">
<a rel="noreferrer nofollow" target="_blank" href="https://github.com/caaster"><img src="https://avatars.githubusercontent.com/u/3210225?v=4" />caaster</a>
commented
<strong> 7 years ago</strong> </div>
<div class="markdown-body">
<p>+1 for documentation of what is not currently available in Spotlight. This would be very helpful to me/ Spotlight service team as well.</p> </div>
</div>
<div class="comment">
<div class="user">
<a rel="noreferrer nofollow" target="_blank" href="https://github.com/caaster"><img src="https://avatars.githubusercontent.com/u/3210225?v=4" />caaster</a>
commented
<strong> 7 years ago</strong> </div>
<div class="markdown-body">
<p>@blalbrit FWIW, Chris explained to me that several of the tickets listed have maintenance implications, making them challenging to implement. I am very interested in how Parker needs are addressed by Spotlight, and to learn whether or not it will be feasible to leverage any Parker-Spotlight work in this vein for Spotlight at Stanford. -- Especially, how generalizable the Parker approach will be, or whether it must be a customized/one-off.</p> </div>
</div>
<div class="comment">
<div class="user">
<a rel="noreferrer nofollow" target="_blank" href="https://github.com/arcadiafalcone"><img src="https://avatars.githubusercontent.com/u/7491842?v=4" />arcadiafalcone</a>
commented
<strong> 7 years ago</strong> </div>
<div class="markdown-body">
<p>@blalbrit @caaster Spreadsheet attached covering what Spotlight does and doesn't index in MODS terms. I set up the data so that you should be able to filter on FALSE in the "Indexed for display?" or "Indexed for faceting?" columns and see everything not currently indexed in either category.</p>
<p><a href="https://github.com/sul-dlss/exhibits/files/777724/spotlight_mods_comprehensive.xlsx">spotlight_mods_comprehensive.xlsx</a></p> </div>
</div>
<div class="comment">
<div class="user">
<a rel="noreferrer nofollow" target="_blank" href="https://github.com/caaster"><img src="https://avatars.githubusercontent.com/u/3210225?v=4" />caaster</a>
commented
<strong> 7 years ago</strong> </div>
<div class="markdown-body">
<p>This ticket has largely been superseded by a number of recast & carefully articulated tickets about metadata indexing & display. I am not closing this ticket yet -- until I determine if we need any of the history captured in this ticket.</p> </div>
</div>
<div class="page-bar-simple">
</div>
<div class="footer">
<ul class="body">
<li>© <script>
document.write(new Date().getFullYear())
</script> Githubissues.</li>
<li>Githubissues is a development platform for aggregating issues.</li>
</ul>
</div>
<script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script>
<script src="/githubissues/assets/js.js"></script>
<script src="/githubissues/assets/markdown.js"></script>
<script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script>
<script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script>
<script>
hljs.highlightAll();
</script>
</body>
</html>