diff --git a/docs/doxygen-user/android_analyzer.dox b/docs/doxygen-user/android_analyzer.dox
index eee20b85a0..e5c1fa8b39 100644
--- a/docs/doxygen-user/android_analyzer.dox
+++ b/docs/doxygen-user/android_analyzer.dox
@@ -33,7 +33,7 @@ The module may also extract data from the following apps:
NOTE: These database formats vary by version of OS and different vendors can place the databases in different places. Autopsy may not support all versions and vendors.
-NOTE: This module is not exhaustive with its support for Android. It was created as a starting point for others to contribute plug-ins for 3rd party apps. See the Developer docs for information on writing modules.
+NOTE: This module is not exhaustive with its support for Android. It was created as a starting point for others to contribute plug-ins for 3rd party apps. See the Developer docs for information on writing modules.
Configuration
diff --git a/docs/doxygen-user/main.dox b/docs/doxygen-user/main.dox
index 1322042b91..6cba09c571 100644
--- a/docs/doxygen-user/main.dox
+++ b/docs/doxygen-user/main.dox
@@ -4,7 +4,7 @@
Overview
-----
-This is the User's Guide for the open source Autopsy platform. Autopsy allows you to examine a hard drive or mobile device and recover evidence from it. This guide should help you with using Autopsy. The developer's guide will help you develop your own Autopsy modules.
+This is the User's Guide for the open source Autopsy platform. Autopsy allows you to examine a hard drive or mobile device and recover evidence from it. This guide should help you with using Autopsy. The developer's guide will help you develop your own Autopsy modules.
Note: For those users running Autopsy on Mac devices, the functionality available through the "Tools" -> "Options" dialog as described in this documentation can be accessed through the system menu bar under "Preferences" or through the Cmd + , (command-comma) shortcut.
diff --git a/docs/doxygen/Doxyfile b/docs/doxygen/Doxyfile
index dd78bc69ea..649fa51fc0 100644
--- a/docs/doxygen/Doxyfile
+++ b/docs/doxygen/Doxyfile
@@ -2061,7 +2061,7 @@ SKIP_FUNCTION_MACROS = YES
# the path). If a tag file is not located in the directory in which doxygen is
# run, you must also specify the path to the tagfile here.
-TAGFILES = $(TSK_HOME)/bindings/java/doxygen/tskjni_doxygen.tag=http://www.sleuthkit.org/sleuthkit/docs/jni-docs/4.3/
+TAGFILES = $(TSK_HOME)/bindings/java/doxygen/tskjni_doxygen.tag=http://www.sleuthkit.org/sleuthkit/docs/jni-docs/latest/
# When a file name is specified after GENERATE_TAGFILE, doxygen will create a
# tag file that is based on the input files it reads. See section "Linking to
diff --git a/docs/doxygen/main.dox b/docs/doxygen/main.dox
index 230be1fd03..4d2664e87f 100644
--- a/docs/doxygen/main.dox
+++ b/docs/doxygen/main.dox
@@ -3,7 +3,7 @@
Overview
Autopsy has been designed as a digital forensics platform to incorporate third-party modules (either open or closed source). This document is for developers who want to write add-on modules or modify the internal Autopsy framework.
-If you are a user and are looking for documentation on how to use Autopsy, refer to the User Docs.
+If you are a user and are looking for documentation on how to use Autopsy, refer to the User Docs.
If these pages don't answer your question, then send the question to the Sleuth Kit Developer's List.
@@ -24,7 +24,7 @@ This document contains the following pages:
- \subpage mod_content_page
- \subpage mod_result_page
- \subpage adv_dev_page
-- Query the Database
+- Query the Database
- \subpage mod_mobile_page
Modifying Autopsy
diff --git a/docs/doxygen/modDSIngestTutorial.dox b/docs/doxygen/modDSIngestTutorial.dox
index c38f3d5814..c187f7ab33 100644
--- a/docs/doxygen/modDSIngestTutorial.dox
+++ b/docs/doxygen/modDSIngestTutorial.dox
@@ -40,7 +40,7 @@ That's it. In the file-level ingest module, we had a shutdown() method, but we d
\subsection python_tutorial2_process The process() Method
-The process method in a data source-level ingest module is passed in reference to the data source as a Content object and a Progress Bar class to update our progress.
+The process method in a data source-level ingest module is passed in reference to the data source as a Content object and a Progress Bar class to update our progress.
For this tutorial, you can start by deleting the contents of the existing process() method in the sample module. The full source code is linked to at the end of this blog and shows more detail about a fully fledged module. We'll just cover the analytics in the blog.
\subsubsection python_tutorial2_getting_files Getting Files
@@ -55,7 +55,7 @@ Our example needs these two lines to get the FileManager for the current case an
fileManager = Case.getCurrentCase().getServices().getFileManager()
files = fileManager.findFiles(dataSource, "contacts.db")\endverbatim
-findFiles() returns a list of AbstractFile objects. This gives you access to the file's metadata and content.
+findFiles() returns a list of AbstractFile objects. This gives you access to the file's metadata and content.
For our example, we are going to open these SQLite files. That means that we need to save them to disk. This is less than ideal because it wastes time writing the data to disk and then reading it back in, but it is the only option with many libraries. If you are doing some other type analysis on the content, then you do not need to write it to disk. You can read directly from the AbstractFile (see the sample modules for specific code to do this).
diff --git a/docs/doxygen/modFileIngestTutorial.dox b/docs/doxygen/modFileIngestTutorial.dox
index 7873513a4f..8079718137 100644
--- a/docs/doxygen/modFileIngestTutorial.dox
+++ b/docs/doxygen/modFileIngestTutorial.dox
@@ -72,7 +72,7 @@ The process() method is passed in a reference to an AbstractFile Object. With th
\verbatim if ((file.getSize() > 10485760) and ((file.getSize() % 4096) == 0)):
\endverbatim
-Now that we have found the files, we want to do something with them. In our situation, we just want to alert the user to them. We do this by making an "Interesting Item" blackboard artifact. The Blackboard is where ingest modules can communicate with each other and with the Autopsy GUI. The blackboard has a set of artifacts on it and each artifact:
+Now that we have found the files, we want to do something with them. In our situation, we just want to alert the user to them. We do this by making an "Interesting Item" blackboard artifact. The Blackboard is where ingest modules can communicate with each other and with the Autopsy GUI. The blackboard has a set of artifacts on it and each artifact:
- Has a type
- Is associated with a file
diff --git a/docs/doxygen/modIngest.dox b/docs/doxygen/modIngest.dox
index a2d81627b9..d2a1696c48 100644
--- a/docs/doxygen/modIngest.dox
+++ b/docs/doxygen/modIngest.dox
@@ -198,7 +198,7 @@ See \ref platform_blackboard for details on saving results to it. You use the
The blackboard defines artifacts for specific data types (such as web bookmarks).
You can use one of the standard artifact types or create your own.
-After you've added an artifact and all of its attributes to the blackboard, you should call sleuthkit.Blackboard.postArtifact(), which will:
+After you've added an artifact and all of its attributes to the blackboard, you should call sleuthkit.Blackboard.postArtifact(), which will:
- Analyze the artifact and add any timestamps to the Timeline tables
- Send an event over the Sleuth Kit event bus that the artifact(s) was added
@@ -212,7 +212,7 @@ This means you no longer have to make separate calls to:
- Index the artifact
- Fire the event to refresh the UI.
-If you are creating a large number of artifacts, you may see better performance if you save all the artifacts you create and do one bulk post at the end using sleuthkit.Blackboard.postArtifacts(). You can also post batches of artifacts instead of saving all of them until the end.
+If you are creating a large number of artifacts, you may see better performance if you save all the artifacts you create and do one bulk post at the end using sleuthkit.Blackboard.postArtifacts(). You can also post batches of artifacts instead of saving all of them until the end.
You should not be using the Autopsy version of Blackboard. Those methods have all been deprecated and is another example of us moving "services" into the TSK data model.
diff --git a/docs/doxygen/modReportModuleTutorial.dox b/docs/doxygen/modReportModuleTutorial.dox
index 26cb14564e..ed2b184cf0 100644
--- a/docs/doxygen/modReportModuleTutorial.dox
+++ b/docs/doxygen/modReportModuleTutorial.dox
@@ -25,7 +25,7 @@ Note that if you look at the \ref mod_report_page "full developer docs", there a
\subsection python_tutorial3_getting_content Getting Content
-With report modules, it is up to you to find the content that you want to include in your report or analysis. Generally, you will want to access some or all of the files, tagged files, or blackboard artifacts. As you may recall from the previous tutorials, blackboard artifacts are how ingest modules in Autopsy store their results so that they can be shown in the UI, used by other modules, and included in the final report. In this tutorial, we will introduce the SleuthkitCase class, which we generally don't introduce to module writers because it has lots of methods, many of which are low-level, and there are other classes, such as FileManager, that are more focused and easier to use.
+With report modules, it is up to you to find the content that you want to include in your report or analysis. Generally, you will want to access some or all of the files, tagged files, or blackboard artifacts. As you may recall from the previous tutorials, blackboard artifacts are how ingest modules in Autopsy store their results so that they can be shown in the UI, used by other modules, and included in the final report. In this tutorial, we will introduce the SleuthkitCase class, which we generally don't introduce to module writers because it has lots of methods, many of which are low-level, and there are other classes, such as FileManager, that are more focused and easier to use.
\subsubsection python_tutorial3_getting_files Getting Files
@@ -37,15 +37,15 @@ fileManager = Case.getCurrentCase().getServices().getFileManager()
for dataSource in dataSources:
files = fileManager.findFiles(dataSource, "%.txt")\endverbatim
-Another approach is to use the SleuthkitCase.findAllFilesWhere() method that allows you to specify a SQL query. To use this method, you must know the schema of the database (which makes this a bit more challenging, but more powerful). The schema is defined on the wiki.
+Another approach is to use the SleuthkitCase.findAllFilesWhere() method that allows you to specify a SQL query. To use this method, you must know the schema of the database (which makes this a bit more challenging, but more powerful). The schema is defined on the wiki.
-Usually, you just need to focus on the tsk_files table. You may run into memory problems and you can also use SleuthkitCase.findAllFileIdsWhere() to get just the IDs and then call SleuthkitCase.getAbstractFileById() to get files as needed.
+Usually, you just need to focus on the tsk_files table. You may run into memory problems and you can also use SleuthkitCase.findAllFileIdsWhere() to get just the IDs and then call SleuthkitCase.getAbstractFileById() to get files as needed.
A third approach is to call org.sleuthkit.autopsy.casemodule.Case.getDataSources(), and then recursively call getChildren() on each Content object. This will traverse all of the folders and files in the case. This is the most memory efficient, but also more complex to code.
\subsubsection python_tutorial3_getting_artifacts Getting Blackboard Artifacts
-The blackboard is where modules store their analysis results. If you want to include them in your report, then there are several methods that you could use. If you want all artifacts of a given type, then you can use SleuthkitCase.getBlackboardArtifacts(). There are many variations of this method that take different arguments. Look at them to find the one that is most convenient for you.
+The blackboard is where modules store their analysis results. If you want to include them in your report, then there are several methods that you could use. If you want all artifacts of a given type, then you can use SleuthkitCase.getBlackboardArtifacts(). There are many variations of this method that take different arguments. Look at them to find the one that is most convenient for you.
\subsubsection python_tutorial3_getting_tags Getting Tagged Files or Artifacts
diff --git a/docs/doxygen/platformConcepts.dox b/docs/doxygen/platformConcepts.dox
index 23389d935b..a272a72191 100644
--- a/docs/doxygen/platformConcepts.dox
+++ b/docs/doxygen/platformConcepts.dox
@@ -52,7 +52,7 @@ The blackboard allows modules to communicate with each other and the UI. It has
The blackboard is not unique to Autopsy. It is part of The Sleuth Kit datamodel and The Sleuth Kit Framework. In the name of reducing the amount of documentation that we need to maintain, we provide links here to those documentation sources.
-- The Blackboard
+- The Blackboard
\subsection mod_dev_other_services Framework Services and Utilities