Workflow:Browsertrix-crawler Workflow - Revision history

Jakebickford: /* Purpose, Context and Content */

2021-12-09T17:02:28Z

Purpose, Context and Content

2021-12-09T17:01:47Z

Further Information

2021-12-09T17:01:16Z

Further Information

2021-12-09T16:57:28Z

Evaluation/Review

2021-12-09T16:56:10Z

Purpose, Context and Content

2021-12-09T16:55:26Z

Purpose, Context and Content

2021-12-09T16:54:50Z

Purpose, Context and Content

2021-12-09T16:50:02Z

Purpose, Context and Content

2021-12-09T16:48:49Z

Purpose, Context and Content

2021-12-09T16:48:27Z

Purpose, Context and Content

@@ Line 20: / Line 20: @@
 <!-- Describe what your workflow is for - i.e. what it is designed to achieve, what the organisational context of the workflow is, and what content it is designed to work with -->
-The purpose of this workflow is determine whether a site is suitable for capture with [https://github.com/webrecorder/browsertrix-crawler Browsertrix Crawler] and if so, run a Browsertrix crawl. The crawl is then subject to Quality Assurance. If the crawl is found to be unsatisfactory Browsertrix settings are adjusted and the crawl is run again, with this process potentially being repeated several times until a satisfactory crawl is completed. If no satisfactory crawl can be made in this way, the site will be captured with Conifer.
+The purpose of this workflow is determine whether a site is suitable for capture with [https://github.com/webrecorder/browsertrix-crawler Browsertrix Crawler] and if so, run a Browsertrix crawl. The crawl is then subject to Quality Assurance. If the crawl is found to be unsatisfactory, Browsertrix settings are adjusted and the crawl is run again, with this process potentially being repeated several times until a satisfactory crawl is completed. If no satisfactory crawl can be made in this way, the site will be captured with Conifer.
 The steps are as follows:

← Older revision		Revision as of 17:01, 9 December 2021
Line 71:		Line 71:
	<!-- Note that your workflow will be marked with a CC3.0 licence -->		<!-- Note that your workflow will be marked with a CC3.0 licence -->

−	Information on getting started with Browsertrix Crawler can be found on the project's [https://github.com/webrecorder/browsertrix-crawler ~~github~~ page].	+	Information on getting started with Browsertrix Crawler can be found on the project's [https://github.com/webrecorder/browsertrix-crawler GitHub page].

← Older revision		Revision as of 17:01, 9 December 2021
Line 70:		Line 70:

	<!-- Note that your workflow will be marked with a CC3.0 licence -->		<!-- Note that your workflow will be marked with a CC3.0 licence -->
		+
		+	Information on getting started with Browsertrix Crawler can be found on the project's [https://github.com/webrecorder/browsertrix-crawler github page].

@@ Line 61: / Line 61: @@
 ==Evaluation/Review==
 <!-- How effective was the workflow? Was it replaced with a better workflow? Did it work well with some content but not others? What is the current status of the workflow? Does it relate to another workflow already described on the wiki? Link, explain and elaborate -->
 ==Further Information==

@@ Line 20: / Line 20: @@
 <!-- Describe what your workflow is for - i.e. what it is designed to achieve, what the organisational context of the workflow is, and what content it is designed to work with -->
-The purpose of this workflow is determine whether a site is suitable for capture with [https://github.com/webrecorder/browsertrix-crawler Browsertrix Crawler] and if so, run a Browsertrix crawl. The crawl is then subject to Quality Assurance. If the crawl is found to be unsatisfactory Browsertrix settings are adjusted and the crawl is run again, with this process potentially being repeated several times until a satisfactory crawl is completed. If not satisfactory crawl can be made in this way, the site will be captured with Conifer.
+The purpose of this workflow is determine whether a site is suitable for capture with [https://github.com/webrecorder/browsertrix-crawler Browsertrix Crawler] and if so, run a Browsertrix crawl. The crawl is then subject to Quality Assurance. If the crawl is found to be unsatisfactory Browsertrix settings are adjusted and the crawl is run again, with this process potentially being repeated several times until a satisfactory crawl is completed. If no satisfactory crawl can be made in this way, the site will be captured with Conifer.
 The steps are as follows:

@@ Line 28: / Line 28: @@
 . The site is assessed to determine which capture method is suitable. At this point we look at:
-     * How large the site is
+* How large the site is
-     * Does the site contain interactive content?
+* Does the site contain interactive content?
-     * What is the planned capture frequency? (if the proposed capture is very frequent we may be more likely to use an in-house tool like Browsertrix to reduce costs)
+* What is the planned capture frequency? (if the proposed capture is very frequent we may be more likely to use an in-house tool like Browsertrix to reduce costs)
-     * What level of fidelity is required
+* What level of fidelity is required
-     * Have previous crawls of the site been attempted and what was the outcome
+* Have previous crawls of the site been attempted and what was the outcome
 . An initial decision of what capture technology to use is made

@@ Line 38: / Line 38: @@
 . If Browsertrix is selected, an initial config will be generated based on our knowledge of the site (in our case this would be generated from our in-house database).
-.
+. An initial Browsertrix is then run, using default settings.
 ==Evaluation/Review==

← Older revision		Revision as of 16:50, 9 December 2021
Line 35:		Line 35:

	3. An initial decision of what capture technology to use is made		3. An initial decision of what capture technology to use is made
		+
		+	4. If Browsertrix is selected, an initial config will be generated based on our knowledge of the site (in our case this would be generated from our in-house database).
		+
		+	5.

	==Evaluation/Review==		==Evaluation/Review==