--
You received this message because you are subscribed to a topic in the Google Groups "archivematica" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/archivematica/cjVNyeHaOJ4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to archivematic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/archivematica/a606b590-1fa1-424e-befa-c63edc46765bn%40googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "archivematica" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/archivematica/cjVNyeHaOJ4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to archivematic...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/archivematica/fa0e734e-4e07-4efc-b7d4-93637496c4bfn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/archivematica/4c882e2f-e21a-4b96-a8f5-7a7d52d38dacn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/archivematica/ee4c0105-db33-4c88-97e6-335fe7e90be9n%40googlegroups.com.
Hi Tatiana,
Great, it would be interesting to compare both solutions.
We have not got good results by using type=”hierarchical”.
We managed to keep hierarchy with <mets:structMap ID="structMap_2" LABEL="Normative Directory Structure" TYPE="logical"> but with two down sides: names were normalized and all folders
(metadata and submissionDocumentation) were created in AtoM. Our goal is to keep original names with diacritic character and original structure in AtoM.
So we developed our own type which is activated by a trigger based on a metadata located in metadata.csv file.
Cheers,
Meilleures salutations
Romain Guedj, e-Archiviste
Romain...@fr.ch, T +41 26 305 13 74
—
Bibliothèque cantonale et universitaire BCU
Kantons- und Universitätsbibliothek KUB
Secteur technologies du web et infrastructure informatique
Abteilung Webtechnologien und Informatik-Infrastruktur
Rue de la Carrière 22, Case postale, 1701 Fribourg
T +41 26 305 13 33, www.fr.ch/bcuf
—
Direction de l’instruction publique, de la culture et du sport DICS
Direktion für Erziehung, Kultur und Sport EKSD
—
ETAT DE FRIBOURG
STAAT FREIBURG
|
P Be green ! Keep it on the screen…
De : archiv...@googlegroups.com <archiv...@googlegroups.com>
De la part de Tatiana Canelhas
Envoyé : mardi 25 mai 2021 17:38
À : archiv...@googlegroups.com
Objet : Re: [archivematica] Re: Create AtoM Directory
To view this discussion on the web visit https://groups.google.com/d/msgid/archivematica/CAGdZUcx1beXm8K39yxWmyw4h0zdWopSQegO%3D5XgUW3e8ZM8dqg%40mail.gmail.com.
Hi Tatiana,
My apologies, I did not mention that our input is an unzipped bag.
Meilleures salutations
Romain Guedj, e-Archiviste
Romain...@fr.ch, T +41 26 305 13 74
—
Bibliothèque cantonale et universitaire BCU
Kantons- und Universitätsbibliothek KUB
Secteur technologies du web et infrastructure informatique
Abteilung Webtechnologien und Informatik-Infrastruktur
Rue de la Carrière 22, Case postale, 1701 Fribourg
T +41 26 305 13 33, www.fr.ch/bcuf
—
Direction de l’instruction publique, de la culture et du sport DICS
Direktion für Erziehung, Kultur und Sport EKSD
—
ETAT DE FRIBOURG
STAAT FREIBURG
|
P Be green ! Keep it on the screen…
De : Guedj Romain
Envoyé : mercredi 26 mai 2021 09:07
À : archiv...@googlegroups.com
Objet : RE: [archivematica] Re: Create AtoM Directory
We have developped our own solution to preserve both elements of an archive in AtoM :
- original names of folder and files (diacritic characters)
- original structure of folder hierarchy.
We forked AtoM to change AtoM behaviour to preserve those elements above when a trigger is present.
The trigger is defined in the metadata.csv file.
This solution could be much more elegant and wider open to various needs or contexts but it works.
Requirement :
- input packet must be a bag with a specific structure.
- if you use an automation tool, you may need to modify the conf of your automation line by adding or modify the following argument. The transfer type must be defined as : --transfer-type 'unzipped bag'
GitHub - artefactual/automation-tools: Tools to aid automation of Archivematica and AtoM.
- modify metadata.csv
Bag structure
Our input packet for archiving a fond is a bag. So an input looks like
xxxxx@bcuipres01_qa:~/FD-KEHREN-OBERSON-ARCHNUMFR_6932-0114$ tree -L 3
.
├── bag-info.txt
├── bagit.txt
├── data
│ └── skip-transfer-directory
│ └── VOL 13.9.07
├── manifest-md5.txt
├── metadata
│ └── metadata.csv
├── processingMCP.xml
└── tagmanifest-md5.txt
VOL 13.9.07 is one of the folders at the root of the original fonds. This folder contains multiple subfolders (not shown in this tree).
We did not managed to keep the original subfolder of the first level in AtoM (exemple here VOL 13.9.07). Our workaround was to create an intermediate folder called skip-transfer-directory between data and original folder of the archive into the bag. (see tree above)
We use to produce one bag per root folder. This archive was delivered on a HD containing 135 folders so we created 135 bags.
We have created a tool to create automatically those specific bags from an archive. BCUF/fd_bagger (github.com)
Metadata file
metadata.csv looks like
parts,dc.title,dc.identifier,bcu.process
objects/,FD-KEHREN-OBERSON-ARCHNUMFR_6932-0114,ARCHNUMFR 6932-0114,hierarchical
Our homemade trigger is bcu.brocess and the value is hierarchical.
When AtoM receives the DIP, it won’t flatten the structure of the archive because the trigger hierarchical is being identified through the METS file.
<mets:dmdSec
ID="dmdSec_3">
<mets:mdWrap MDTYPE="OTHER"
OTHERMDTYPE="CUSTOM">
<mets:xmlData>
<bcu_process>hierarchical</bcu_process>
</mets:xmlData>
</mets:mdWrap>
</mets:dmdSec>
Then we add a new behavior (see the commit at GitHub - BCUF/atom at stable/2.6.x )
- to get the original names of files and folder
- to remove the intermediate folder created in the bag ( skip-transfer-directory )
See attached capture of original folder of the archive, bag structure and the result in AtoM