forked from terrywbrady/File-Analyzer
-
Notifications
You must be signed in to change notification settings - Fork 11
File Analyzer Training Code4Lib 2014
Terry Brady edited this page Mar 3, 2014
·
24 revisions
- Install and build the File Analyzer (required): Installation instructions
- Send Terry a quick note confirming that you were able to complete the installs. At the end of the pre-conference session, we will code a custom File Analyzer rule. In your email, indicate your level of experience/comfort programming in Java. This portion of the session will be tailored to the experience of the audience.
- A Java IDE is recommended for last portion of the pre-conference. If you do not already have a Java IDE available, consider installing the Eclipse Standard Edition: https://www.eclipse.org/downloads/
- File Analyzer Overview
- Try it yourself
- Demonstration of highly customized File Analyzer Rules
- Your ideas for future customizations
- Coding a File Analyzer rule
User documentation is available at the link listed above.
- User Interface: Search the File System
- User interface: viewing results
- Sorting results
- Filtering results
- Exporting results
- User interface: import records from a file
- User interface: Merging and Comparing Results
Sample data files corresponding to these exercises will be provided at the start of the pre-conference session.
- Run "Count Files by Type" on the "01_Flash Drive Inventory" folder. ** Sort the results from highest count to lowest count. What file type occurs most frequently?
- Run "Match by Name" on the "01_Flash Drive Inventory" folder. ** Which file names have been duplicated? ** Remove your open tabs
- Run "Match by Base Name" ** on the PDF folder ** run it again on the Word Docs folder ** Which word document does not have a corresponding PDF?
- Remove the tabs from all of your prior tests.
- Run "Sort by Checksum" looking only at image files ** on the Checksum Tests folder. ** run it again on the Checksum Tests2 folder. ** Which files are not identical between the 2 folders? ** Remove the tab for your test on the Checksum Tests2 folder. ** Export the results from your first "Sort by Checksum" task as a tab-delimited file. Export only the key and data fields. ** Import your checksum results using "Import Delimited File" ** Use the merge tool to compare your imported file to the results from your checksum test ** No differences should exist
- Counter compliant report validation
- Output to Bursar processing
- Invoice processing
- Identify digital derivatives
- ETD Processing