AIP/DIP File Folder Schema Rationale

[Dan Noonan at The OSU]

Hello All: As I am working through testing the use of Archivematica at Ohio State I am running into a series of questions/concerns, but will trying to address them thematically or by subject.

First off, I'm trying to understand the rationale for the file foldering schema that is created for AIPs and DIPs (and I would assume SIPs).

Why does Archivematica create a series of nested folders based upon a deconstructed UUID? Why all the empty nested folders that ultimately creates a longer file path string?

Wouldn't it be more efficient to just append the UUID to the bagged payload name either as a prefix or suffix?

From a human readable and interactive point-of-view this seems particularly cumbersome way to handle this information.

Any insight folks could provide would be helpful.

Thank you - Dan

[Dan Noonan at The OSU]

Forgot to include the graphic

[Elin Jonsson]

Hello Dan!

I think you will find the answer here:

https://groups.google.com/g/archivematica/c/R0efBWCaI0c/m/EY2Jfbn9CAAJ

Hope this helps!

Elin,

Sydarkivera 

--
You received this message because you are subscribed to the Google Groups "archivematica" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archivematic...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/archivematica/319adfde-1747-4274-90c1-d20ea6fa9716n%40googlegroups.com.

[Dan Noonan at The OSU]

Thanks Elin, that does explain it!