Twitter and Tear Gas

Master case overview

Master file reference

GPRCC-ILL-2017-ZT-805327

Illustrative status

On Hold

Author / reference identity

Zeynep Tufekci

Subject area

Technology & Society

Work

Twitter and Tear Gas

Review focus

Technology terminology, data provenance and time-sensitive technical claims. Program questions are selected for this subject area; no passage-level findings are asserted.

Proposed formats · scenario

Print, ebook and audiobook

Proposed market scope · scenario

English-language release; foreign editions subject to separate review

Book release date

16 May 2017
Publication record ↗

Registration date · illustrative

23 May 2017

Publication and registration basis

Twitter and Tear Gas: Original book release; replaces later-edition or year-only catalog metadata. The modeled registration is seven days after release. Where a source gives only a month or year, dates are shown as a range rather than inventing a day.

Modeled review date

23 June 2017

Source basis

Library title, author, subject mapping and catalog program definitions; no manuscript examined.

Programs & status

This illustrative file covers 9 program records, 36 review controls and 23 open items. Select a program for its review details, document checklist and next action.

Program reference

GPRCC-ILL-2017-ZT-805327-DPCP

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

1 of 4 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 4

1. DPCP-102

   Use and consent basis

   For the proposed scope of Twitter and Tear Gas, document the proposed basis and scope for identifiable case-study material. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

2. DPCP-103

   Minimization

   For the proposed scope of Twitter and Tear Gas, consider whether unnecessary identifying details can be removed. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

3. DPCP-104

   Access controls

   For the proposed scope of Twitter and Tear Gas, separate public material from restricted review records. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

4. DPCP-105

   Retention scope

   For the proposed scope of Twitter and Tear Gas, define retention and deletion rules for review copies. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

Requirements to complete 4

• Consent and use-basis checklistClarification neededThe scenario requires clarification of scope before this item can close. Reference: DPCP-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Minimization and redaction worksheetRequiredThe scenario leaves this evidence item outstanding. Reference: DPCP-103.Awaiting submission · illustrative
• Review access planCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: DPCP-104.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Retention scheduleClarification neededThe scenario requires clarification of scope before this item can close. Reference: DPCP-105.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2017-ZT-805327-AICP

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

2 of 4 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 4

1. AICP-101

   Content provenance

   For the proposed scope of Twitter and Tear Gas, identify whether any proposed publication assets use generated material. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

2. AICP-102

   Human review

   For the proposed scope of Twitter and Tear Gas, define responsibility for checking any generated passages or visual assets. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

3. AICP-103

   Input rights

   For the proposed scope of Twitter and Tear Gas, document permission boundaries for inputs used in proposed generation workflows. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

4. AICP-105

   Version history

   For the proposed scope of Twitter and Tear Gas, track edited outputs and the responsible human reviewer. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

Requirements to complete 4

• AI-use declaration checklistRequiredThe scenario leaves this evidence item outstanding. Reference: AICP-101.Awaiting submission · illustrative
• Human review protocolCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: AICP-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Input provenance registerCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: AICP-103.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Generation and revision logClarification neededThe scenario requires clarification of scope before this item can close. Reference: AICP-105.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2017-ZT-805327-NDIS

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

2 of 3 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 3

1. NDIS-101

   Source provenance

   For the proposed scope of Twitter and Tear Gas, trace research inputs to their origin and document verification limits. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

2. NDIS-102

   Confidentiality handling

   For the proposed scope of Twitter and Tear Gas, separate public references from material requiring restricted access. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

3. NDIS-104

   Interview permission

   For the proposed scope of Twitter and Tear Gas, document the scope of any proposed interview reuse. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

Requirements to complete 3

• Source provenance registerCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: NDIS-101.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Source handling matrixCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: NDIS-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Interview permission checklistRequiredThe scenario leaves this evidence item outstanding. Reference: NDIS-104.Awaiting submission · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2017-ZT-805327-FCRS

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

1 of 3 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 3

1. FCRS-101

   Claim inventory

   For the proposed scope of Twitter and Tear Gas, classify factual, historical and statistical claims selected for the review scope. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

2. FCRS-102

   Source traceability

   For the proposed scope of Twitter and Tear Gas, record author, date, edition and location of supporting references. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

3. FCRS-104

   Data reproduction

   For the proposed scope of Twitter and Tear Gas, reconcile quoted figures with their source tables and units. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

Requirements to complete 3

• Claim-to-source ledgerClarification neededThe scenario requires clarification of scope before this item can close. Reference: FCRS-101.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Source bibliography and locator indexCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: FCRS-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Statistical reproduction worksheetRequiredThe scenario leaves this evidence item outstanding. Reference: FCRS-104.Awaiting submission · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2017-ZT-805327-PDTC

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

2 of 5 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 5

1. PDTC-101

   Platform scope

   For the proposed scope of Twitter and Tear Gas, identify target platforms and the formats proposed for delivery. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

2. PDTC-102

   Terms mapping

   For the proposed scope of Twitter and Tear Gas, map the proposed release against documented platform requirements. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

3. PDTC-103

   Metadata consistency

   For the proposed scope of Twitter and Tear Gas, align categories, descriptions and edition identifiers across platforms. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

4. PDTC-104

   Access and files

   For the proposed scope of Twitter and Tear Gas, specify file validation and accessibility checks before delivery. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

5. PDTC-105

   Change handling

   For the proposed scope of Twitter and Tear Gas, assign responsibility for updates, corrections and withdrawal requests. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

Requirements to complete 5

• Platform delivery matrixCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: PDTC-101.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Platform requirements checklistClarification neededThe scenario requires clarification of scope before this item can close. Reference: PDTC-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Digital metadata sheetCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: PDTC-103.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Digital file validation checklistClarification neededThe scenario requires clarification of scope before this item can close. Reference: PDTC-104.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Platform change-control planRequiredThe scenario leaves this evidence item outstanding. Reference: PDTC-105.Awaiting submission · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2017-ZT-805327-IDLC

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

2 of 4 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 4

1. IDLC-102

   License boundaries

   For the proposed scope of Twitter and Tear Gas, map term, format, territory, language and sublicensing limits. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

2. IDLC-103

   Retail metadata

   For the proposed scope of Twitter and Tear Gas, reconcile title, author credit, edition description and rights-holder attribution. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

3. IDLC-104

   Accounting and reporting

   For the proposed scope of Twitter and Tear Gas, document royalty reporting intervals, deductions and audit provisions. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

4. IDLC-105

   Termination controls

   For the proposed scope of Twitter and Tear Gas, define takedown, stock sell-off and rights reversion responsibilities. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

Requirements to complete 4

• Distribution license matrixCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: IDLC-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Retail metadata approval sheetClarification neededThe scenario requires clarification of scope before this item can close. Reference: IDLC-103.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Royalty and reporting scheduleCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: IDLC-104.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Termination and reversion checklistRequiredThe scenario leaves this evidence item outstanding. Reference: IDLC-105.Awaiting submission · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2017-ZT-805327-IRTC

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

2 of 5 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 5

1. IRTC-101

   Chain of title

   For the proposed scope of Twitter and Tear Gas, identify the party authorized to grant rights and reconcile contributor assignments. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

2. IRTC-102

   Territory and format scope

   For the proposed scope of Twitter and Tear Gas, map languages, formats, exclusivity and reserved territories without assuming worldwide rights. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

3. IRTC-103

   Edition history

   For the proposed scope of Twitter and Tear Gas, separate original publication rights from revised-edition and supplementary-material rights. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

4. IRTC-104

   Quotation permissions

   For the proposed scope of Twitter and Tear Gas, record the basis for reuse of any third-party extracts in the proposed edition. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

5. IRTC-105

   Reversion and reservations

   For the proposed scope of Twitter and Tear Gas, identify expired grants, reserved uses and conflicting options. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

Requirements to complete 5

• Ownership and contributor assignment scheduleCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: IRTC-101.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Territory, language and format matrixCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: IRTC-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Edition and rights chronologyClarification neededThe scenario requires clarification of scope before this item can close. Reference: IRTC-103.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Third-party permissions registerRequiredThe scenario leaves this evidence item outstanding. Reference: IRTC-104.Awaiting submission · illustrative
• Prior grants and reversion scheduleClarification neededThe scenario requires clarification of scope before this item can close. Reference: IRTC-105.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2017-ZT-805327-CAVR

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

1 of 5 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 5

1. CAVR-101

   Visual asset provenance

   For the proposed scope of Twitter and Tear Gas, record the source and permitted use of cover and interior visual assets. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

2. CAVR-102

   Designer permissions

   For the proposed scope of Twitter and Tear Gas, separate designer deliverables from third-party stock and font licenses. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

3. CAVR-103

   Format reuse

   For the proposed scope of Twitter and Tear Gas, check proposed visual reuse across print, ebook, audio and promotion. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

4. CAVR-104

   Credit requirements

   For the proposed scope of Twitter and Tear Gas, record mandatory image credits and license conditions. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

5. CAVR-105

   Edition approval

   For the proposed scope of Twitter and Tear Gas, track the approved cover version for each proposed edition. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Completed · scenario. The submitted evidence is accepted in this scenario; other requirements remain open.

Requirements to complete 5

• Cover and artwork provenance registerClarification neededThe scenario requires clarification of scope before this item can close. Reference: CAVR-101.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Designer and supplier rights checklistClarification neededThe scenario requires clarification of scope before this item can close. Reference: CAVR-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Visual reuse permission matrixClarification neededThe scenario requires clarification of scope before this item can close. Reference: CAVR-103.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Visual credit-line sheetRequiredThe scenario leaves this evidence item outstanding. Reference: CAVR-104.Awaiting submission · illustrative
• Cover version approval logCompletedThe submitted evidence is accepted in this scenario; other requirements remain open. Reference: CAVR-105.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative

↑ Back to programs

Program reference

GPRCC-ILL-2017-ZT-805327-IBEM

Master file

GPRCC-ILL-2017-ZT-805327

Review scope

Print, ebook and audiobook

Evidence position

0 of 3 controls complete in scenario

Publication context

Twitter and Tear Gas by Zeynep Tufekci · Technology terminology, data provenance and time-sensitive technical claims

Review controls and outstanding items 3

1. IBEM-101

   Protected assets

   For the proposed scope of Twitter and Tear Gas, separate protectable text and artwork from third-party names and lawful references. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Required · scenario. The scenario leaves this evidence item outstanding.

2. IBEM-102

   Authorized channels

   For the proposed scope of Twitter and Tear Gas, distinguish approved editions and sellers from items that need verification. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

3. IBEM-105

   Notice readiness

   For the proposed scope of Twitter and Tear Gas, specify evidence capture and rights-holder approval before any proposed notice. Apply this check in the context of technology terminology, data provenance and time-sensitive technical claims.

   Clarification needed · scenario. The scenario requires clarification of scope before this item can close.

Requirements to complete 3

• Protected asset inventoryRequiredThe scenario leaves this evidence item outstanding. Reference: IBEM-101.Awaiting submission · illustrative
• Authorized edition and channel registerClarification neededThe scenario requires clarification of scope before this item can close. Reference: IBEM-102.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative
• Evidence capture and escalation protocolClarification neededThe scenario requires clarification of scope before this item can close. Reference: IBEM-105.Submission attempt 1 · 28 May 2017 · reviewed 23 June 2017 · illustrative

↑ Back to programs

Evidence and document index

A modeled evidence schedule for Twitter and Tear Gas. These are document requirements and scenario states, not uploaded attachments or manuscript citations.

Consolidated program status

Illustrative review history

Generated milestones showing how this workflow could progress; these events did not occur for the named author.

Program fee breakdown

The original illustrative case total is allocated across the 9 programs below. These example amounts are not payment receipts or quotations.

Total illustrative fees · USD$30,500

These restored case allocations are separate from the planning bands for new quotes. A written scope and quote determine the charge for an actual matter.

Next steps

1. Reconcile outstanding documents against the program references in the evidence index.
2. Prepare one coordinated completion package with edition, rights and source schedules.
3. Review each open item and record whether it is resolved, requires clarification or needs specialist referral.
4. Issue any subsequent determination only after the evidence review is complete.

This sequence describes the modeled on hold workflow only.