New Deposits - Revision history

Abyrne at 16:37, 8 May 2025

2025-05-08T16:37:09Z

← Older revision		Revision as of 16:37, 8 May 2025
Line 249:		Line 249:

	:'''Location of logs:'''		:'''Location of logs:'''
			When reporting an issue, please include the log from your Documents folder as an attachment to assist in troubleshooting.


	::[[File:Location of logs.png\|border]]		::[[File:Location of logs.png\|border]]

Abyrne at 19:09, 6 May 2025

2025-05-06T19:09:13Z

← Older revision		Revision as of 19:09, 6 May 2025
Line 230:		Line 230:

	::[[File:ie_csv_export_3.png\|700px\|border]]		::[[File:ie_csv_export_3.png\|700px\|border]]

			==Debugging==

			Debugging is new with version 3.6.6. It is a feature that allows a user to toggle debugging on and off. Turning debugging on will produce verbose logs to look through if the Processor crashes or if there are errors that require further investigation.

			Logs are now automatically created in the user’s Documents folder, so no need to remember to save. The log starts when you open the app and is appended to as you work.

			===Debugging settings===

			You can toggle the settings in the File menu and clicking on Settings. Selecting Debugging will create more verbose logs that will automatically save in your Documents folder.

			::[[File:Debugging_settings.png\|border]]

			:'''How the verbose logs look:'''

			::[[File:Verbose_logs.png\|border]]


			:'''Location of logs:'''


			::[[File:Location of logs.png\|border]]

Abyrne at 15:47, 29 July 2024

2024-07-29T15:47:13Z

← Older revision		Revision as of 15:47, 29 July 2024
Line 15:		Line 15:


	::[[File:Organize 2.PNG\|border]]		::[[File:Organize 2.PNG\|600px\|border]]


Line 71:		Line 71:


	::[[File:CSV fields.PNG\|border]]		::[[File:CSV fields.PNG\|600px\|border]]

Abyrne at 15:40, 24 July 2024

2024-07-24T15:40:49Z

← Older revision		Revision as of 15:40, 24 July 2024
Line 176:		Line 176:


	::[[File:METS fields.PNG\|border]]		::[[File:METS fields.PNG\|500px\|border]]

Abyrne at 19:26, 5 December 2022

2022-12-05T19:26:47Z

Abyrne: Added Rosetta ingest fixity check details

2022-12-05T19:15:41Z

Added Rosetta ingest fixity check details

← Older revision		Revision as of 19:15, 5 December 2022
Line 79:		Line 79:

	==Running Fixity in the Processor==		==Running Fixity in the Processor==
	The Rosetta processor allows staff to generate MD5 checksums to include in a CSV deposit. There is also an option to verify a previously generated fixity manifest to check that the files have not changed. Review CJH's generation and verification recommendations [https://wiki.cjh.org/index.php/Checksum_generation_and_verification_recommendations here].		The Rosetta processor allows staff to generate MD5 checksums to include in a CSV deposit. There is also an option to verify a previously generated fixity manifest to check that the files have not changed.

			Rosetta will verify the checksums in the deposit CSV during the ingest process. If a file's MD5 checksum does not the match the checksum listed in the deposit CSV, the deposit will land in the Technical Analyst workbench for further review.

			Review CJH's fixity generation and verification recommendations [https://wiki.cjh.org/index.php/Checksum_generation_and_verification_recommendations here].

	===Process Requirements===		===Process Requirements===

Abyrne: Added fixity instructions

2022-12-05T18:48:48Z

Added fixity instructions

@@ Line 77: / Line 77: @@
 ::- The log will provide the path for the deposit folder. This folder can be copied to the appropriate submissions folder for Rosetta ingest.
 ::- An example of a successful CSV process log can be [[Media:CSV log.txt|viewed here]].
 ==Dublin Core Process==

Kpowell: /* Synchronize */

2020-05-26T01:25:37Z

Synchronize

← Older revision		Revision as of 01:25, 26 May 2020
Line 148:		Line 148:
	::- The default ArchivesSpace link caption is "View Online." If you'd like to customize that caption, use the IE CSV input method		::- The default ArchivesSpace link caption is "View Online." If you'd like to customize that caption, use the IE CSV input method
	: '''3. Update Rosetta IE with Aleph -> DC or ArchivesSpace -> DC metadata.'''		: '''3. Update Rosetta IE with Aleph -> DC or ArchivesSpace -> DC metadata.'''
	:: - ~~The Processor prioritizes~~ Aleph IDs over ArchivesSpace ~~ids for metadata synchronization~~. ~~However~~, if an IE has both an Aleph and ArchivesSpace ID, the Processor will still see whether the Archival Object in ArchivesSpace needs a link.		:: - '''New with 2.5''': Now staff can choose which system's metadata record to synchronize with Rosetta. Choosing "Default" from the right-hand list options will prioritize Aleph IDs that are found over ArchivesSpace IDs that are found. Regardless, if an IE has both an Aleph and ArchivesSpace ID, the Processor will still see whether the Archival Object in ArchivesSpace needs a link.

	=== IE CSV ===		=== IE CSV ===

Kpowell: /* Exporting an IE CSV */

2019-12-12T15:58:18Z

Exporting an IE CSV

← Older revision		Revision as of 15:58, 12 December 2019
Line 169:		Line 169:
	:'''2. Add custom ASPACE CAPTION column if desired'''		:'''2. Add custom ASPACE CAPTION column if desired'''

	::[[File:ie_csv_export_2.png\|border]]		::[[File:ie_csv_export_2.png\|700px\|border]]

Kpowell: /* Synchronize */

2019-12-12T15:57:44Z

Synchronize

← Older revision		Revision as of 15:57, 12 December 2019
Line 131:		Line 131:
	The Synchronize tab is new with Version 2.0. It replaces the Sip Status module and the Add DAO Tab. DAO linking is now rolled into the synchronization job. To learn how to check on a SIP's status using the Rosetta software, see [http://wiki.cjh.org/index.php/How_to_Check_SIP_Status this tutorial].		The Synchronize tab is new with Version 2.0. It replaces the Sip Status module and the Add DAO Tab. DAO linking is now rolled into the synchronization job. To learn how to check on a SIP's status using the Rosetta software, see [http://wiki.cjh.org/index.php/How_to_Check_SIP_Status this tutorial].

	::[[File:sync.png~~\|700px~~\|border]]		::[[File:sync.png\|border]]

	===Requirements===		===Requirements===

← Older revision		Revision as of 19:26, 5 December 2022
Line 89:		Line 89:
	:*'''A fixity manifest.		:*'''A fixity manifest.
	::- Only required if opting to verify a previously generated fixity manifest to check that the files have not changed.		::- Only required if opting to verify a previously generated fixity manifest to check that the files have not changed.
	::- A fixity manifest should include a list of the files with file paths and the ~~file’s md5~~ checksum.		::- A fixity manifest should include a list of the files with file paths and the files' MD5 checksum.
	::- The tools listed [https://wiki.cjh.org/index.php/Checksum_generation_and_verification_recommendations#Fixity_check_tools here] can generate a fixity manifest.		::- The tools listed [https://wiki.cjh.org/index.php/Checksum_generation_and_verification_recommendations#Fixity_check_tools here] can generate a fixity manifest.
	::- An example of a fixity manifest can be [[Media:SampleFixityManifest.txt\|viewed here]].		::- An example of a fixity manifest can be [[Media:SampleFixityManifest.txt\|viewed here]].
Line 104:		Line 104:

	:*'''Click the Submit button.'''		:*'''Click the Submit button.'''
	::- The processor will create a deposit CSV with ~~the~~ MD5 checksum value for each file in the V column.		::- The processor will create a deposit CSV with a MD5 checksum value for each file in the V column.
	::- An example of a deposit CSV with MD5 checksum values can be [[Media:SampleDepositCSVWithChecksums.csv\|viewed here]].		::- An example of a deposit CSV with MD5 checksum values can be [[Media:SampleDepositCSVWithChecksums.csv\|viewed here]].

Line 124:		Line 124:
	:*'''Click the Submit button'''		:*'''Click the Submit button'''
	::- The processor will create a deposit CSV with a MD5 checksum value for each file in the V column.		::- The processor will create a deposit CSV with a MD5 checksum value for each file in the V column.
	::- If the checksums in the fixity manifest ~~does~~ not match the checksums generated by the processor, the processor will display an error like the following and will not create the deposit.		::- If the checksums in the fixity manifest do not match the checksums generated by the processor, the processor will display an error like the following and will not create the deposit.