Kris Dekeyser
My feedback
12 results found
-
2 votesKris Dekeyser
shared this idea
·
-
3 votesKris Dekeyser
shared this idea
·
-
4 votesKris Dekeyser
shared this idea
·
-
4 votes
An error occurred while saving the comment Kris Dekeyser
shared this idea
·
-
2 votes
An error occurred while saving the comment Kris Dekeyser
commented
You may want to be very careful in doing this. I ran the 'Identify storage dead references' task chain on our repository and it created a new version for each IE. It got our database setup into problems because the archivelogs were filling up faster than they could be processed by the DB dataguard. See case #00480085.
My intention was not even to update the checksums, but merely to check the files, but a bug caused the process to recalculate the checksum and create an event for each IE, causing the update and a new version for each IE in the system. But that's another story...
So, if you are expecting to perform the IE updates at a high rate, I would strongly recommend to make a full DB backup first, then turn off archivelogs and other time-critical settings before starting the update of 22 million IE's.
-
20 votesKris Dekeyser
supported this idea
·
-
5 votes
-
1 voteKris Dekeyser
shared this idea
·
-
7 votes
An error occurred while saving the comment Kris Dekeyser
commented
"tab indentation" ... make that Markdown syntax and I would be happy too ;)
-
15 votes
An error occurred while saving the comment Kris Dekeyser
commented
Adi,
In reality things work differently. When an archive institution assigns a retention period, it expects to be notified when the retention period expires. However, only when they explicitly decide at that moment that the data may indeed be deleted, an actual delete can be performed. Without confirmation the data must be retained until further notice.
This is literally what we read in the RFPs of archiving institutions (I suspect it is even a European guideline). The reasoning is that retention policies are typically assigned by dossier type, but often the AI will want to keep data longer due to special interest, recent activities, high demand, ... The appreciation of the proper retention policy for an individual dossier can often only be made after many years.
The reporting part in Rosetta is OK, but not the fact that the retention policy will automatically delete, which makes it fairly simple for Rosetta to comply. The option to delete permanently or not should be replaced with a 3-way option: no action / move to recycle bin / delete permanently.
Kris Dekeyser
supported this idea
·
-
33 votesKris Dekeyser
supported this idea
·
-
21 votes
Adi Alter
responded
Submitted by Ex Libris PM on behalf of our customers
Kris Dekeyser
supported this idea
·
Hi Daniel,
We are currently not yet on version 6.1, so I cannot test it yet. But from what I understand from your explanation, will it be possible to combine both? I mean to generate a descriptive MD field on the fly using the XSL and use that for the share URL?
If not, on what granularity can the Share URL link be hidden? Global, Institution, Delivery Rule, ... ?