Hi Kiriaki, If you want all items to be flagged as "unpublished", then I'd recommend your idea to have a custom non-interactive step that sets all items to "unpublished" (and therefore all items will get dc.date.issued auto-assigned again). In fact, this should be a simple code change:
First, you should make sure to enable the SkipInitialQuestionsStep in your item-submission.xml config (it is enabled by default, but you should double check you didn't previously disable it): https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/item-submission.xml#L189 Then, you can customize the existing "SkipInitialQuestionsStep" to set "publishedBefore(false)" (it defaults to true). In this line of code, change the true to false: https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/submit/step/SkipInitialQuestionsStep.java#L56 You will then need to recompile DSpace (mvn package) and redeploy (ant update). After that, all your items should be flagged as "unpublished" and dc.date.issued should be auto-assigned again. Good luck, Tim On Fri, May 18, 2018 at 6:52 AM Kiriaki Roditi <[email protected]> wrote: > Hello Tim, > > > > Thank you for the reply. > > Every item submitted would be “unpublished”, so I would like to avoid > enabling the initial questions. I am afraid it will confuse the end-users > that submit their theses. > > Could I automatically set every item submitted as “unpublished”, so that I > could avoid end-user intervention per submission? What do you think is the > best way to work around that? > > Maybe add a custom non-interactive step in the submission process to set > *publishedBefore=false* or perhaps this can be stated by setting an > appropriate metadata field value in each collection’s template? > > Or, should I edit the code that was modified in Pull Request 373 > <https://github.com/DSpace/DSpace/pull/373/files>? > > Is there something else I can’t think of? > > > > Greetings, > > Kiriaki > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Tim Donohue > *Sent:* Thursday, May 17, 2018 5:54 PM > *To:* Kiriaki Roditi <[email protected]> > *Cc:* [email protected] > *Subject:* Re: [dspace-tech] Re-enable dc.date.issued auto-assignment > > > > Hello Kiriaki, > > The "dc.date.issued" field is now only auto-assigned if you enable the > "Initial Questions" page and select that the item is "unpublished" (i.e. > not previously published before). This new behavior is described here: > https://wiki.duraspace.org/display/DSDOC6x/Metadata+Recommendations#MetadataRecommendations-RecommendedMetadataFields > > > > The behavior was changed in DSpace 4.0 because of complaints about > incorrect/inaccurate dates in Google Scholar and Google search results. > Both of those search engines based their results off our "dc.date.issued" > field, and when that field was auto-assigned, it sometimes resulted in very > odd search results in Google. See these two old tickets for more details: > * https://jira.duraspace.org/browse/DS-1481 > > * https://jira.duraspace.org/browse/DS-1745 > > > > I hope that helps, > > > > Tim > > > > > > On Thu, May 17, 2018 at 3:57 AM Kiriaki Roditi <[email protected]> > wrote: > > Hello, > > > > We have just upgraded our 3.1 DSpace installation to 6.2 and found out > that dc.date.issued in not assigned automatically anymore. > > Our repository contains only Theses which are submitted by their authors, > so we would like dc.date.issued to be set to the day the item is archived > into the repository, as always. What would be the best way to do that? > > > > Thank you in advance, > > Kiriaki > > > > -- > 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. > > -- > > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > > -- > 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. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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.
