I should have specified that we're currently running DSpace 3.6 but going to upgrade to Dspace 6.0 once everything is stable. WLR
On Thursday, December 7, 2017 at 10:30:42 AM UTC-9, [email protected] wrote: > > Thank you very much! I was waiting for a quiet time to set it to a very > low number but, if the default is > zero, then that obviously won't solve the issue. > > Walter R. > > On Wednesday, December 6, 2017 at 5:54:55 AM UTC-9, Mark H. Wood wrote: >> >> On Tuesday, December 5, 2017 at 7:11:54 PM UTC-5, [email protected] >> wrote: >>> >>> In the dspace.cfg file if a setting with a value is commented out it >>> typically is showing the default value. >>> We have a user who isn't seeing updates to the communities and >>> collections. I found this line in the >>> dspace.cfg file which *might* be the culprit: >>> #xmlui.community-list.cache = 12 hours >>> >>> I'm accustomed to times being specified in numeric seconds or sometimes >>> minutes. This is unusual. >>> >>> Does that mean that 12hrs is the default value used by DSpace if a new >>> value isn't specified? What if >>> our site is relatively small with few changes. Can it be turned off >>> completely by setting it to zero (0)? >>> And what is the format of the time? Could I set >>> xmlui.community-list.cache = 1 minute? 30 seconds? >>> >>> I've searched the manual and online but didn't find the answer to these >>> question. So, any insight you >>> can provide is greatly appreciated. >>> >>> >> >> As one might suppose, the code is in dspace-xmlui. Specifically it is in >> org.dspace.app.xmlui.aspect.artifactbrowser.CommunityBrowser. The value of >> xmlui.community-list.cache is passed to >> org.dspace.app.xmlui.util.DSpaceValidity.setAssumedValidityDelay, where it >> is parsed: >> * This method takes a string which is parsed for the delay time, the >> string >> * must be of the following form: "<integer> <scale>" where scale is >> days, >> * hours, minutes, or seconds. >> * >> * Examples: "1 day" or "12 hours" or "1 hour" or "30 minutes" >> The code does accept either singular or plural and doesn't care if this >> matches the number -- "1 days" or "33 minute" will be accepted. The unit >> of measure is required. >> >> It appears that, if unconfigured, the cache validity period is zero: the >> underlying objects will always be checked for changes. The numeric value >> is not checked in any way, so long as it is indeed a Java long integer, so >> you could set it to zero if you wish, but I think that will have the same >> effect as leaving it unconfigured. >> >> >> -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
