Copied in bulk

This page is generated from the code and must not be edited by hand.

A folder copied in all at once (five or more files, four in five created after they were last changed, all within ten minutes) is asked about only where its times make a later step, such as an analysis, look older than the raw data it came from.

copied_in_bulk version 2+d1

• Kind of rule: What is raised for attention (flags). Raises something for a person’s attention without concluding anything.

• What it concludes: a finding

• Reasoning: defeasible. A conclusion is usually right, and is retracted when a rule it names concludes against it.

• What it reads: one folder at a time

Is it available in this version?

Yes. The engine runs it.

What would defeat it

A finding is never withdrawn. When any of these rules also concludes about the same thing, the finding records it:

• installed_software_in_folder: A folder is recognized as an installed program, such as a copy of Fiji or a Python environment, from the parts it holds, a name ending .app, its program-style subfolders or a majority of program files; its files are still indexed and read, and rules about experiments leave them alone.

It stands aside beneath every folder one of these rules raises:

• installed_software_in_folder

Parameters

Parameter	Shipped value	May be	What it does
minimum_files	5	whole number, from 2 to 100000	How many files with a birth the folder must directly hold.
minimum_share	0.8	number, from 0 to 1	The share of them that must be born after their modification.
burst_window_seconds	600	whole number, from 1 to 604800	How close together their births must be.
stage_rules	["acquisition_stage_from_format", "pipeline_stage_from_name", "analysis_stage_from_derived_sense"]	list of text	The rules whose conclusions place a file at a stage.
entry_stages	["raw", "acquisition"]	list of text	The stages where data enters.
time_rule	"earliest_credible_time"	text	The rule whose conclusion says when a file first existed.