In our newly migrated DSpace 5.3 instance, I found a typo in our crontab so that the index-authority command was failing its nightly run at 12:45 am. I corrected that problem.
Today I find that the last_modified date has been set to a minute or so after 12:45 am this morning for 7723 items. This is a bit distressing since last_modified date affects OAI harvesting. Is this just a phenomenon of being on a new server? Now that index-authority has been run will it not affect last_modified from now on? -- 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 http://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
