James,
We have noticed the same issue while publishing content via the API. A
dc.description.provenance field is created, but is not updated when
bitstreams are added. Here is an example of what we get:
dc.description.provenance Made available in DSpace on
2017-04-25T21:33:20Z (GMT). No. of bitstreams: 0
Have you found out any more information about addressing this issue?
Thanks!
Ed Warga
On Wednesday, September 28, 2016 at 5:05:13 PM UTC-5, Creel, James Silas
wrote:
>
> Hi Everybody,
>
>
>
> We have an application where our librarians can curate and publish items
> to our DSpace 5.4 repository with the REST API. The push is accomplished
> with a sequence of requests, first to create the item, then several more
> requests to upload some files and set the bundles and permissions of them.
>
>
>
> We’re finding that the dc.provenance metadatum is created only on the
> initial item creation and so reports that there are 0 bitstreams. We never
> were able to get the REST API to work with a single request for
> multiple-file multiple-bundle items with permissions, so we had to take
> this sequenced approach. Obviously, we would like dc.provenance generated
> after the item has been completely assembled. It looks like a bit of
> development work, then – does it make sense to implement a transactional
> approach to the REST calls or to rework the API to take a much more
> complicated package in a single request?
>
>
>
> I welcome any thoughts or suggestions.
>
>
>
> Thanks,
>
>
>
> James Creel
>
--
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
