Create METHODOLOGY.md
Browse files- METHODOLOGY.md +50 -0
METHODOLOGY.md
ADDED
|
@@ -0,0 +1,50 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Methodology
|
| 2 |
+
|
| 3 |
+
## Objective
|
| 4 |
+
|
| 5 |
+
The dataset organizes source-linked information that helps print shops research printable media and printer workflows without turning preliminary research into unsupported certification claims.
|
| 6 |
+
|
| 7 |
+
## Source selection
|
| 8 |
+
|
| 9 |
+
Priority is given to:
|
| 10 |
+
|
| 11 |
+
1. Official manufacturer product pages.
|
| 12 |
+
2. Official technical bulletins or product information bulletins.
|
| 13 |
+
3. Brand-controlled application or workflow pages.
|
| 14 |
+
|
| 15 |
+
Secondary commentary is not used as the sole support for a technical compatibility statement in this release.
|
| 16 |
+
|
| 17 |
+
## Collection and normalization
|
| 18 |
+
|
| 19 |
+
- A researcher records the source URL, brand or topic, workflow context, and intended use.
|
| 20 |
+
- Product and printer family names are preserved as written by the source when practical.
|
| 21 |
+
- Multi-value fields use semicolon-separated values in CSV and remain strings in JSONL.
|
| 22 |
+
- Source review dates use ISO `YYYY-MM-DD` format.
|
| 23 |
+
- Missing values are left blank rather than inferred.
|
| 24 |
+
|
| 25 |
+
## Claim-risk labels
|
| 26 |
+
|
| 27 |
+
- `High`: exact performance, warranty, certification, equivalency, durability, or cross-brand compatibility should be verified before publication.
|
| 28 |
+
- `Medium`: official source context exists, but application-specific performance still requires current documentation and testing.
|
| 29 |
+
- Blank: the source library does not assign a claim-risk score.
|
| 30 |
+
|
| 31 |
+
## Quality controls
|
| 32 |
+
|
| 33 |
+
- CSV files must have a stable header and consistent column count.
|
| 34 |
+
- JSONL output must contain one valid JSON object per non-empty line.
|
| 35 |
+
- Source URLs must use HTTP or HTTPS.
|
| 36 |
+
- Dataset row totals must reconcile with the release manifest.
|
| 37 |
+
- Technical compatibility is described as workflow context unless the cited source explicitly supports a stronger claim.
|
| 38 |
+
|
| 39 |
+
## Update policy
|
| 40 |
+
|
| 41 |
+
This release is a dated snapshot. Future releases should:
|
| 42 |
+
|
| 43 |
+
1. Recheck source availability and product status.
|
| 44 |
+
2. Record changed URLs or specifications.
|
| 45 |
+
3. Preserve prior tagged releases for auditability.
|
| 46 |
+
4. Increment the dataset version and publish a changelog.
|
| 47 |
+
|
| 48 |
+
## Responsible use
|
| 49 |
+
|
| 50 |
+
Users should confirm current manufacturer documentation, ICC/profile requirements, ink compatibility, laminate pairing, surface preparation, and application conditions. Production samples and controlled testing remain necessary.
|