Staging loaders are working mostly as expected. I noticed two things while testing:
1) When uploading files to a private collection, the core files will remain private even if the sentinel is set to make the core file public. This makes sense since we don't allow public files in private collections. Just to make it a bit clearer to the user (me!), can the public/private Sentinel options for core files in a private collection behave like permissions for files or collections contained within a private collection? In other words, if a collection is private, the collection's Sentinel should not allow me to try to make new files "public".
Staging loaders are working mostly as expected. I noticed two things while testing:
1) When uploading files to a private collection, the core files will remain private even if the sentinel is set to make the core file public. This makes sense since we don't allow public files in private collections. Just to make it a bit clearer to the user (me!), can the public/private Sentinel options for core files in a private collection behave like permissions for files or collections contained within a private collection? In other words, if a collection is private, the collection's Sentinel should not allow me to try to make new files "public".
2) The depositor ID isn't being added to the rights records for some derivative files. I tested a few different files using the Marcom loader: http://cerberus.library.northeastern.edu/collections/neu:6241
I tested Sentinel derivative options using these two files: http://cerberus.library.northeastern.edu/files/neu:dr26zb235 http://cerberus.library.northeastern.edu/files/neu:dr26zb24f
These are the Sentinel settings:
The loader applied these permissions, but the large derivative files are missing the depositor ID:
I uploaded these two files in an earlier load to test uploading with just collection permission:
For these files, the large derivative files do have the depositor ID under "edit".