Finding aid aggregation - Revision history

Smcintyre: /* Searching and Browsing */

2010-03-30T21:49:45Z

Searching and Browsing

← Older revision		Revision as of 15:49, 30 March 2010
Line 132:		Line 132:
	'''Institutional Search and Browse''': Once you have created your EAD collection in CONTENTdm and uploaded files to it, your users will be able to use standard CONTENTdm features to search and browse your EAD files. In addition, you may create special search and browse pages using CONTENTdm's Custom Query Report functions. For an example, see the University of Utah Marriott Library's search/browse page in the Special Collections section at http://www.lib.utah.edu (click "Search Finding Aids" on the Special Collections main page).		'''Institutional Search and Browse''': Once you have created your EAD collection in CONTENTdm and uploaded files to it, your users will be able to use standard CONTENTdm features to search and browse your EAD files. In addition, you may create special search and browse pages using CONTENTdm's Custom Query Report functions. For an example, see the University of Utah Marriott Library's search/browse page in the Special Collections section at http://www.lib.utah.edu (click "Search Finding Aids" on the Special Collections main page).

	'''Central Search and Browse in MWDL''' ~~[not yet available]~~: The metadata from all uploaded EAD files ~~will be~~ harvested periodically and aggregated into the Mountain West Digital Library at http://mwdl.org. Search and browse pages within MWDL's interface will allow users to discover finding aids from all partners, or from any selected subset of the ~~partners. Sandra McIntyre and Nathan Pugh are creating interface mockups for both searching and browsing for consideration by the LSTA~~ partners.		'''Central Search and Browse in MWDL''': The metadata from all uploaded EAD files is harvested periodically and aggregated into the Mountain West Digital Library at http://mwdl.org. Search and browse pages within MWDL's interface will allow users to discover finding aids from all partners, or from any selected subset of the partners.

Smcintyre: /* Directions */

2010-03-30T21:48:34Z

Directions

← Older revision		Revision as of 15:48, 30 March 2010
Line 77:		Line 77:
	:'''Important note re date ranges (for CONTENTdm 4.3 only -- this issue is resolved in CONTENTdm 5):'''		:'''Important note re date ranges (for CONTENTdm 4.3 only -- this issue is resolved in CONTENTdm 5):'''

	:After importing the records into the Project Spreadsheet, carefully examine the Date column. There is a bug in CONTENTdm, and some date ranges do not expand correctly and will need to be edited.		:After importing the records into the Project Spreadsheet, carefully examine the Date column. There is a bug in CONTENTdm 4, and some date ranges do not expand correctly and will need to be edited.

	:CONTENTdm's import should have expanded most date ranges from the format yyyy-yyyy into the expanded list of years. For example, "1813-1815" will be expanded automatically into "1813; 1814; 1815". However, when CONTENTdm encounters a date range that spans a century or more, it mangles it instead into an incorrect date with the format yyyy-01-dd. For example, "1898-1905" is converted to "1898-01-05".		:CONTENTdm's import should have expanded most date ranges from the format yyyy-yyyy into the expanded list of years. For example, "1813-1815" will be expanded automatically into "1813; 1814; 1815". However, when CONTENTdm 4 encounters a date range that spans a century or more, it mangles it instead into an incorrect date with the format yyyy-01-dd. For example, "1898-1905" is converted to "1898-01-05".

	:If you catch these errors before you have uploaded the records, by looking through the values in the Date column in the Project Spreadsheet, you can correct them fairly easily:		:If you catch these errors before you have uploaded the records, by looking through the values in the Date column in the Project Spreadsheet, you can correct them fairly easily:

Smcintyre: /* 1. Extracting the EAD Elements */

2010-03-30T21:47:20Z

1. Extracting the EAD Elements

← Older revision		Revision as of 15:47, 30 March 2010
Line 34:		Line 34:
	=== 1. Extracting the EAD Elements ===		=== 1. Extracting the EAD Elements ===

	An extraction script has been created to automate the first step. The extraction script has been written in ~~VBScript~~ by Nathan Pugh at the University of Utah, based on a VBScript created by Terry Reese at Oregon State University. Nate has tailored this script for the LSTA project partners.		An extraction script has been created to automate the first step. The extraction script has been written in JSE by Nathan Pugh at the University of Utah, based on a VBScript created by Terry Reese at Oregon State University. Nate has re-organized and tailored this script for the LSTA project partners, complete with a logger.

	==== Summary of the Process ====		==== Summary of the Process ====

Smcintyre: /* Overview of Aggregation Process */

2010-03-30T21:43:44Z

Overview of Aggregation Process

← Older revision		Revision as of 15:43, 30 March 2010
Line 7:		Line 7:
	The EAD collections for the LSTA-funded project are available locally by institution, as well as searchable and browsable centrally in the MWDL statewide index. Each EAD file exists in only one place, namely, on the local repository. When a user searches or browses the central index, and clicks on a item of interest in the search/browse results, he or she is taken to the EAD file on the local repository. Users can search locally as well, but they get results only from the local institution when conducting a local search. A link allows them to go to the central MWDL index at any time.		The EAD collections for the LSTA-funded project are available locally by institution, as well as searchable and browsable centrally in the MWDL statewide index. Each EAD file exists in only one place, namely, on the local repository. When a user searches or browses the central index, and clicks on a item of interest in the search/browse results, he or she is taken to the EAD file on the local repository. Users can search locally as well, but they get results only from the local institution when conducting a local search. A link allows them to go to the central MWDL index at any time.

	For more information about the process described below, please contact Sandra McIntyre (mailto:sandra.mcintyre@utah.edu)~~, Nathan Pugh (mailto:nathan.pugh@utah.edu)~~, or Debbie Rakhsha (mailto:debbie.rakhsha@utah.edu) at the University of Utah Marriott Library.		For more information about the process described below, please contact Sandra McIntyre (mailto:sandra.mcintyre@utah.edu) at the Mountain West Digital Library, or Debbie Rakhsha (mailto:debbie.rakhsha@utah.edu) at the University of Utah Marriott Library.

	== Configuring CONTENTdm for Your EAD Collection ==		== Configuring CONTENTdm for Your EAD Collection ==

Smcintyre: /* Directions */

2010-03-04T00:13:02Z

Directions

← Older revision		Revision as of 18:13, 3 March 2010
Line 107:		Line 107:
	==== Directions ====		==== Directions ====

	Download the complete package of files, '''[[Media:EAD_LSTA_package-~~rev12~~.zip\|EAD_LSTA_package-~~rev12~~.zip]]''' prepared by Nathan Pugh.		Download the complete package of files, '''[[Media:EAD_LSTA_package-rev13.zip\|EAD_LSTA_package-rev13.zip]]''' prepared by Nathan Pugh in 2008 and slightly edited by Sandra McIntyre in November 2009.

	Read the README file, '''[[Media:LSTA EAD stylesheet installation instructions.pdf\|LSTA EAD stylesheet installation instructions.pdf]]''' for complete instructions. You will need to copy some files to appropriate folders on your CONTENTdm server and change one of the PHP files. Optionally, you can change the XSL transform file or, more likely, the CSS stylesheet file, to suit your institution's particular needs.		Read the README file, '''[[Media:LSTA EAD stylesheet installation instructions.pdf\|LSTA EAD stylesheet installation instructions.pdf]]''' for complete instructions. You will need to copy some files to appropriate folders on your CONTENTdm server and change one of the PHP files. Optionally, you can change the XSL transform file or, more likely, the CSS stylesheet file, to suit your institution's particular needs.

Smcintyre: /* Searching and Browsing */

2009-12-01T18:17:04Z

Searching and Browsing

← Older revision		Revision as of 12:17, 1 December 2009
Line 130:		Line 130:
	== Searching and Browsing ==		== Searching and Browsing ==

	'''Institutional Search and Browse''': Once you have created your EAD collection in CONTENTdm and uploaded files to it, your users will be able to use standard CONTENTdm features to search and browse your EAD files. In addition, you may create special search and browse pages using CONTENTdm's Custom Query Report functions.		'''Institutional Search and Browse''': Once you have created your EAD collection in CONTENTdm and uploaded files to it, your users will be able to use standard CONTENTdm features to search and browse your EAD files. In addition, you may create special search and browse pages using CONTENTdm's Custom Query Report functions. For an example, see the University of Utah Marriott Library's search/browse page in the Special Collections section at http://www.lib.utah.edu (click "Search Finding Aids" on the Special Collections main page).

	'''Central Search and Browse in MWDL''' [not yet available]: The metadata from all uploaded EAD files will be harvested periodically and aggregated into the Mountain West Digital Library at http://mwdl.org. Search and browse pages within MWDL's interface will allow users to discover finding aids from all partners, or from any selected subset of the partners. Sandra McIntyre and Nathan Pugh are creating interface mockups for both searching and browsing for consideration by the LSTA partners.		'''Central Search and Browse in MWDL''' [not yet available]: The metadata from all uploaded EAD files will be harvested periodically and aggregated into the Mountain West Digital Library at http://mwdl.org. Search and browse pages within MWDL's interface will allow users to discover finding aids from all partners, or from any selected subset of the partners. Sandra McIntyre and Nathan Pugh are creating interface mockups for both searching and browsing for consideration by the LSTA partners.

Smcintyre: /* Directions */

2009-12-01T18:12:28Z

Directions

← Older revision		Revision as of 12:12, 1 December 2009
Line 75:		Line 75:
	Use the tab-delimited text file you created above, ead-to-cdm-extraction.txt. If you have created the CONTENTdm fields in the order listed above, the mapping from imported field to collection field will be correct by default. You do not need to add any import actions using the Template Creator.		Use the tab-delimited text file you created above, ead-to-cdm-extraction.txt. If you have created the CONTENTdm fields in the order listed above, the mapping from imported field to collection field will be correct by default. You do not need to add any import actions using the Template Creator.

	:'''Important note re date ranges:'''		:'''Important note re date ranges (for CONTENTdm 4.3 only -- this issue is resolved in CONTENTdm 5):'''

	:After importing the records into the Project Spreadsheet, carefully examine the Date column. There is a bug in CONTENTdm, and some date ranges do not expand correctly and will need to be edited.		:After importing the records into the Project Spreadsheet, carefully examine the Date column. There is a bug in CONTENTdm, and some date ranges do not expand correctly and will need to be edited.

Smcintyre: /* Directions */

2009-06-03T00:40:55Z

Directions

← Older revision		Revision as of 18:40, 2 June 2009
Line 47:		Line 47:

	# If you have not already done so, save the file '''[[Media:ead-to-cdm-extraction_v2.jse.zip\|ead-to-cdm-extraction_v2.jse.zip]]''' to a local drive. The script will work only on a Windows machine.		# If you have not already done so, save the file '''[[Media:ead-to-cdm-extraction_v2.jse.zip\|ead-to-cdm-extraction_v2.jse.zip]]''' to a local drive. The script will work only on a Windows machine.
	# Unzip the file. The unzipped file is called "ead-to-cdm-~~extraction~~.jse". (The file was zipped to allow the transfer of the file over the Internet. Most systems will not allow an executable file to be transferred on its own.)		# Unzip the file. The unzipped file is called "ead-to-cdm-extraction_v2.jse". (The file was zipped to allow the transfer of the file over the Internet. Most systems will not allow an executable file to be transferred on its own.)
	# Move or copy the extraction script file, ead-to-cdm-~~extraction~~.jse, into the same directory as the EAD files you want to process. All files that you want to process must be in one folder. Remove from this folder any files that you don't want to process at this time. Please note that the EAD files in this folder must already be validated and ready to upload.		# Move or copy the extraction script file, ead-to-cdm-extraction_v2.jse, into the same directory as the EAD files you want to process. All files that you want to process must be in one folder. Remove from this folder any files that you don't want to process at this time. Please note that the EAD files in this folder must already be validated and ready to upload.
	# Double-click the extraction script file and wait for it to process all the EAD files in the folder. Depending on the number and size of your EAD files, this may take anywhere from a fraction of a second to 30 or more seconds. An alert will appear when the processing is done, giving the number of files processed successfully. Click the "OK" button in the alert window. Note that a new file, called ead-to-cdm-extraction.txt, has been created in the same folder (or, if you have already run the script before, the existing file has been modified). This is the tab-delimited text file that you will use in Step 2 below. Also, a logging file called "_extraction_status.txt" is created, which should make it easier to determine which, if any, files are causing the batch extraction to fail.		# Double-click the extraction script file and wait for it to process all the EAD files in the folder. Depending on the number and size of your EAD files, this may take anywhere from a fraction of a second to 30 or more seconds. An alert will appear when the processing is done, giving the number of files processed successfully. Click the "OK" button in the alert window. Note that a new file, called ead-to-cdm-extraction.txt, has been created in the same folder (or, if you have already run the script before, the existing file has been modified). This is the tab-delimited text file that you will use in Step 2 below. Also, a logging file called "_extraction_status.txt" is created, which should make it easier to determine which, if any, files are causing the batch extraction to fail.

Smcintyre: /* Directions */

2009-06-03T00:40:28Z

Directions

← Older revision		Revision as of 18:40, 2 June 2009
Line 46:		Line 46:
	See the full procedure with screenshots, '''[[Media:xEADImporttraining_v3f.pdf\|"Using CONTENTdm's Multiple File Import Feature to Import EAD Files"]]''', or follow the brief set of steps below.		See the full procedure with screenshots, '''[[Media:xEADImporttraining_v3f.pdf\|"Using CONTENTdm's Multiple File Import Feature to Import EAD Files"]]''', or follow the brief set of steps below.

	# If you have not already done so, save the file '''[[Media:ead-to-cdm-~~extraction~~.jse.zip\|ead-to-cdm-~~extraction~~.jse.zip]]''' to a local drive. The script will work only on a Windows machine.		# If you have not already done so, save the file '''[[Media:ead-to-cdm-extraction_v2.jse.zip\|ead-to-cdm-extraction_v2.jse.zip]]''' to a local drive. The script will work only on a Windows machine.
	# Unzip the file. The unzipped file is called "ead-to-cdm-extraction.jse". (The file was zipped to allow the transfer of the file over the Internet. Most systems will not allow an executable file to be transferred on its own.)		# Unzip the file. The unzipped file is called "ead-to-cdm-extraction.jse". (The file was zipped to allow the transfer of the file over the Internet. Most systems will not allow an executable file to be transferred on its own.)
	# Move or copy the extraction script file, ead-to-cdm-extraction.jse, into the same directory as the EAD files you want to process. All files that you want to process must be in one folder. Remove from this folder any files that you don't want to process at this time. Please note that the EAD files in this folder must already be validated and ready to upload.		# Move or copy the extraction script file, ead-to-cdm-extraction.jse, into the same directory as the EAD files you want to process. All files that you want to process must be in one folder. Remove from this folder any files that you don't want to process at this time. Please note that the EAD files in this folder must already be validated and ready to upload.

Smcintyre: /* Directions */

2009-06-02T22:41:55Z

Directions

← Older revision		Revision as of 16:41, 2 June 2009
Line 107:		Line 107:
	==== Directions ====		==== Directions ====

	Download the complete package of files, '''[[Media:~~EAD_LSTA_package_v01~~.zip\|~~EAD_LSTA_package_v01~~.zip]]''' prepared by Nathan Pugh.		Download the complete package of files, '''[[Media:EAD_LSTA_package-rev12.zip\|EAD_LSTA_package-rev12.zip]]''' prepared by Nathan Pugh.

	Read the README file, '''[[Media:LSTA EAD stylesheet installation instructions.pdf\|LSTA EAD stylesheet installation instructions.pdf]]''' for complete instructions. You will need to copy some files to appropriate folders on your CONTENTdm server and change one of the PHP files. Optionally, you can change the XSL transform or, more likely, the CSS stylesheet, to suit your institution's particular needs.		Read the README file, '''[[Media:LSTA EAD stylesheet installation instructions.pdf\|LSTA EAD stylesheet installation instructions.pdf]]''' for complete instructions. You will need to copy some files to appropriate folders on your CONTENTdm server and change one of the PHP files. Optionally, you can change the XSL transform file or, more likely, the CSS stylesheet file, to suit your institution's particular needs.

	Once your IT staff has configured CONTENTdm, you will be able to do the following:		Once your IT staff has configured CONTENTdm, you will be able to do the following:

	# Browse your EAD collection in CONTENTdm by going into your Digital Collections page and selecting the EAD collection. You will see a results page listing the first ~~20 or so~~ of your EAD files.		# Browse your EAD collection in CONTENTdm by going into your Digital Collections page and selecting the EAD collection. You will see a results page listing the first set of your EAD files.

	# Click any file in the results list to view it.		# Click any file in the results list to view it.