Re: [dspace-tech] Re: date.accessioned v. date.available

[Sean Carte]

Thanks for the info, Tim.

Sean

On Thu, 19 Oct 2023 at 21:39, DSpace Technical Support <
dspace-tech@googlegroups.com> wrote:

> Hi Sean,
>
> This has been a discussion for some time. See this older thread:
> https://groups.google.com/g/dspace-tech/c/k7qCSJVhRrU
>
> There's also a ticket that describes the behavior in DSpace 7 here:
> https://github.com/DSpace/DSpace/issues/6583
>
> And, some recent work to fix the issue here:
> https://github.com/DSpace/DSpace/pull/9103  (This is under consideration
> for 8.0).
>
> To summarize: the "availability" time is no longer in metadata (in the new
> Embargo system, which is required in 7.x). Embargo related info is now only
> stored on the access policies (Edit Item -> Status -> Authorizations). More
> discussion also in this ticket:
> https://github.com/DSpace/DSpace/issues/9071
>
> Tim
>
> On Thursday, October 19, 2023 at 6:49:59 AM UTC-5 DSpace Technical Support
> wrote:
>
>> What is the difference between date.accessioned and date.available?
>>
>> According to the documentation:
>>
>> Once any workflow process is successfully and positively completed, the
>> InProgressSubmission object is consumed by an "item installer", that
>> converts the InProgressSubmission into a fully blown archived item in
>> DSpace. The item installer:
>> Assigns an accession date
>> Adds a "date.available" value to the Dublin Core metadata record of the
>> item
>> Adds an issue date if none already present
>>
>> And the metadata descriptions are as follows:
>> date accessioned¹ Date DSpace takes possession of item.
>> date available¹ Date or date range item became available to the public.
>>
>> But on the items I've checked, the date.accessioned and date.available
>> are identical. Even in items where the provenance shows three days between
>> submission and availability.
>>
>> I would have expected date.accessioned to be closer to the submission
>> date. But I suppose there's the date.submitted for that, though that
>> doesn't seem to be auto-populated.
>>
>> date
>>
>> submitted
>>
>> Recommend for theses/dissertations.
>> Is the description.provenance field the only way to determine the time
>> between submission and availability?
>>
>> Sean
>>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> 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/77c24370-fe19-435c-9330-21ad9900294en%40googlegroups.com
> 
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/CA%2BxAuhMgUUVhvNrEBmkkCepxAwVEWx87zc7sO59xVX3neenurQ%40mail.gmail.com.

[dspace-tech] Re: date.accessioned v. date.available

[DSpace Technical Support]

Hi Sean,

This has been a discussion for some time. See this older 
thread: https://groups.google.com/g/dspace-tech/c/k7qCSJVhRrU

There's also a ticket that describes the behavior in DSpace 7 
here: https://github.com/DSpace/DSpace/issues/6583

And, some recent work to fix the issue 
here: https://github.com/DSpace/DSpace/pull/9103  (This is under 
consideration for 8.0).

To summarize: the "availability" time is no longer in metadata (in the new 
Embargo system, which is required in 7.x). Embargo related info is now only 
stored on the access policies (Edit Item -> Status -> Authorizations). More 
discussion also in this ticket: https://github.com/DSpace/DSpace/issues/9071

Tim

On Thursday, October 19, 2023 at 6:49:59 AM UTC-5 DSpace Technical Support 
wrote:

> What is the difference between date.accessioned and date.available?
>
> According to the documentation:
>
> Once any workflow process is successfully and positively completed, the 
> InProgressSubmission object is consumed by an "item installer", that 
> converts the InProgressSubmission into a fully blown archived item in 
> DSpace. The item installer:
> Assigns an accession date
> Adds a "date.available" value to the Dublin Core metadata record of the 
> item
> Adds an issue date if none already present
>
> And the metadata descriptions are as follows:
> date accessioned¹ Date DSpace takes possession of item.
> date available¹ Date or date range item became available to the public.
>
> But on the items I've checked, the date.accessioned and date.available are 
> identical. Even in items where the provenance shows three days between 
> submission and availability.
>
> I would have expected date.accessioned to be closer to the submission 
> date. But I suppose there's the date.submitted for that, though that 
> doesn't seem to be auto-populated.
>
> date
>
> submitted
>
> Recommend for theses/dissertations.
> Is the description.provenance field the only way to determine the time 
> between submission and availability?
>
> Sean
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/77c24370-fe19-435c-9330-21ad9900294en%40googlegroups.com.