Problem: Folder may not end related to a Collection in the automatic import process

[jraddaoui]

At this point, a relation between a Folder (DIP) and a parent Collection is assumed in some parts of the application. But, in the automatic upload (#2), that relation may not happen as the application will look for the access system id in the METS file to associate the new Folder with an existing Collection, and that id may not be present or a Collection may not be found with it.

Therefore, a few changes should be taken in consideration:

• Check that a relation with a Collection actually exists where that assumption is made.
• Allow to set/change the parent Collection after Folder creation.
• Right now, the Folders are accessible through the parent Collection and the children files pages, so it won't be easy to find Folders that are not related. We could create an "Orphan Folders" page (only visible by editors and administrators?) to ease the finding of such Folders.
• Similar to the files from Folders that failed in the import process, this files could be hidden in the search page, for all or only some types of users.

[stefanabreitwieser]

Hi @jraddaoui -- this all makes a lot of sense to me! I agree that "orphan folders" and failed imports should only be seen by editors and administrators. Let me know if there's anything you have questions about, but this looks good to me. :)