Thanks Jerome, Not quite, but it might be feasible to adapt this functionality for my purposes. What I am trying to do is the following: The harvester is picking up records and puts them into CDS Invenio. I have created some collections which pick up the documents of interest, which is essentially a subset of the harvested documents (all theses of a particular university). The documents within such a collection are now exported by someone via excel and processed further outside CDS-invenio. This person would now be interested in being able to pick up the incremental addions to this collection since they exported the documents last. While there is the alerting functionality which in my view would solve this matter, they actually would like to do this whenever they wanted it and not being bound on a regular schedule. While it would be possible to simply keep track of the dates and restric the documents of a given collection using the date limitation functionality, it would be nice to be able to somewhat do this in a simple link (i.e. use in a query for a collection).
If I understand the new feature you mentioned, there would be a staging area where the latest additions would be queued before being promoted to be viewable. Will those "pre-release" documents be already within the database, i.e. searchable or would they simply be queued before being loaded into the repository? If it is the former, then I could see a way around my problem. The later might not solve my problem. Alternatively, I was thinking of possibly doing this by adding a field for each document, which indicates whether the document was already exported or not. However, I would then have to batch update all those fields after it being exported to excel. Do you think this would be feasible? If so, do you have some pointers? Thanks again for all your help. Regards Sergio On Wed, Oct 29, 2008 at 5:13 PM, CDS Support <[email protected]> wrote: > Dear Sergio, > > If I understand well, what you are trying to achieve is a workflow to > review the > updated (harvested) records before they are integrated into the repository? > > If yes, then you might want to wait for a future release of CDS Invenio: we > have > implemented this kind of workflow into the BibHarvest module. > > Let us know if that matches your expectations. > > PS: you might want to write (and subscribe) to the > <[email protected]> > mailing list instead of <[email protected]>, so that other CDS Invenio > users > can also answer based on their experience, and benefit from yours. > > Best regards, > Jerome Caffaro, for CDS Support > > Le 29 oct. 08 à 11:43, Sergio Laberer a écrit : > > > Good day, >> >> I have the following problem to solve and wondered whether you could give >> me some pointers as of where to start off best (I assume that I will have to >> actually go in and do some programming to achieve the following): >> >> I am currently harvesting a bunch of universities and have set up >> collections for each university showing me all the documents which are of >> interest to me for that particular university. >> It is now wished that whenever the documents are exported via excel that >> this somewhat defines the point in time from which forward any incremental >> updates should be captured. Ideally I would create a new set of collections >> only showing the update since the last export occured. >> To do so, I should be able to track the day and time when the excel was >> triggered in the database (so this is my first question: which file do I >> need to look at to do so). Then I somewhat would need a variable which I >> could use in the query holding the last time such an export occured and use >> this variable as the lower boundary of time. >> Not sure whether I explained all of this well enough to be understandable, >> but any help is much appreciated. >> >> Kind Regards >> Sergio >> > >
