Michelle Lindlar
My feedback
10 results found
-
9 votesMichelle Lindlar supported this idea ·
-
33 votesMichelle Lindlar shared this idea ·
-
20 votesMichelle Lindlar supported this idea ·
-
5 votesMichelle Lindlar supported this idea ·
-
10 votesMichelle Lindlar supported this idea ·
-
7 votes
An error occurred while saving the comment An error occurred while saving the comment Michelle Lindlar commentedHi Hörg. Thanks for your comment! The problem is that we want to use the UI based process for staff users who aren't capable to write code to interface with the system.
Since there already are export routines included within the UI (for both single IE exports out of the permanent webeditor as well as batch processes) but there is unfortunately no way to see when they are complete, we thought that this might be useful.Michelle Lindlar shared this idea · -
5 votesMichelle Lindlar supported this idea ·
-
5 votesMichelle Lindlar shared this idea ·
-
2 votes
An error occurred while saving the comment Michelle Lindlar commentedYes, our "ideal" scenario was also that extraction worked in METS deposit worfklows. The path towards discovering that the extract funtionality didn't work in this case was a painful one ;-)
We value the flexibility benefits of the METS deposit such as multi-rep and pre-ingest fixitiy values etc., but also frequently have deposits including zip packages. I'm wondering - would you see the extraction as a permanent action, meaning that an exported AIP would contain the extracted files? Or as a temporary measurement within the archive, where an export would have to include the zip container?Michelle Lindlar shared this idea · -
2 votesMichelle Lindlar shared this idea ·
We will look into the Webservice for automatic processes though. Thanks for pointing this out!