Hi Tim, Wow! The moment I read that specific line in discovery.xml that you mentioned, I knew right away what caused the dc.date.accessioned_dt field to be missing in my solr search core. I modified that line from dc.date.accessioned into dc.date.issued so that it will prevent the newly submitted OLD publications from displaying in the 'Recently Added' block on the home page and in the 'Recent Submissions' on the community and collection home page. The reason for this is that we want to highlight the new publications. I didn't realize that this will be the side effect. I guess I will have to look for other ways to suppress showing old publications that were recently submitted.
Thank you so much for this! Euler On Wednesday, May 13, 2020 at 5:52:30 AM UTC+8, Tim Donohue wrote: > > Hi Euler, > > I'd recommend checking your DSpace logs closely for errors while running a > full reindex. It's possible that an error is causing the > dc.date.accessioned field to not be indexed properly. > > You also should double check that your discovery.xml is the same on both > sites. That file configures which fields are indexed as *dates* (instead > of strings) to support various searches/facets. So, for example, the > Recent Submission configuration area is one that specifies that it needs > the 'dc.date.accessioned' field to be indexed _as a date_: > https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/spring/api/discovery.xml#L249-L253 > > If you've modified the default configurations in discovery.xml this can > affect what fields will be indexed. Additionally, if errors occur during > indexing, fields are often just skipped over entirely. So, that's why it's > important to look in the logs during indexing if you are finding issues > with specific fields. > > Good luck and hopefully that gives you a few clues of what to possibly > look for. > > Tim > ------------------------------ > *From:* dspac...@googlegroups.com <javascript:> <dspac...@googlegroups.com > <javascript:>> on behalf of euler <esn...@seafdec.org.ph <javascript:>> > *Sent:* Tuesday, May 12, 2020 1:21 AM > *To:* DSpace Technical Support <dspac...@googlegroups.com <javascript:>> > *Subject:* [dspace-tech] dc.date.accessioned_dt is missing > > Dear All, > > We recently migrated to a new server and I upgraded the version from 5.5 > to 5.10 and then to 6.3. Before I moved it to the new server, I tested the > migration first in my local instance. Previously, I posted this query last > 2018 in which I asked about SOLR query for submitted items: > https://groups.google.com/d/msg/dspace-tech/TCQlqVNOYcg/myxLBO3vCgAJ. I > am flabbergasted to find out that after upgrading to the latest stable > version, I am still having the same issue. I am really wondering why is it > that there are no dc.date.accessioned_dt in the solr search core of our > production server while in my local instance it is there? I stop tomcat, > deleted the [dspace]/solr/search/data directory and run index-discovery -b > but still no dc.date.accessioned_dt. I also run index-discovery -bf with > the same results. I also deleted the conf directory and replaced it with a > copy from my local instance but still no dc.date.accessioned_dt field. What > could be the cause of this discrepancy when my local instance is [almost] a > replica of our production server but our production server don't have > dc.date.accessioned_dt? > > Please help on how to resolve this because I really needed the > dc.date.accessioned_dt metadata for submitted items SOLR query. > > Thanks in advance! > euler > > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to dspac...@googlegroups.com <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/dspace-tech/00c81008-06cf-41a6-97d7-87526a90df50%40googlegroups.com > > <https://groups.google.com/d/msgid/dspace-tech/00c81008-06cf-41a6-97d7-87526a90df50%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/ca943fbd-d4b0-4b88-9de7-bf6c0a941ac6%40googlegroups.com.
