This README.txt file was generated on 20200818 by Michael Coblenz. # # General instructions for completing README: # For sections that are non-applicable, mark as N/A (do not delete any sections). # Please leave all commented sections in README (do not delete any text). # ------------------- GENERAL INFORMATION ------------------- 1. Title of Dataset: Obsidian vs. Solidity RCT Replication Package # # Authors: Include contact information for at least the # first author and corresponding author (if not the same), # specifically email address, phone number (optional, but preferred), and institution. # Contact information for all authors is preferred. # 2. Author Information First Author Contact Information Name: Michael Coblenz Institution: Carnegie Mellon University Address: 5000 Forbes Ave. Email: mcoblenz@cs.cmu.edu Phone Number: Corresponding Author Contact Information Name: Michael Coblenz Institution: Carnegie Mellon University Address: 5000 Forbes Ave. Email: mcoblenz@cs.cmu.edu Phone Number: Author Contact Information (if applicable) Name: Jonathan Aldrich Institution: Carnegie Mellon University Address: 5000 Forbes Ave. Email: jonathan.aldrich@cs.cmu.edu Phone Number: Name: Brad A. Myers Institution: Carnegie Mellon University Address: 5000 Forbes Ave. Email: bam@cs.cmu.edu Phone Number: Name: Joshua Sunshine Institution: Carnegie Mellon University Address: 5000 Forbes Ave. Email: bam@cs.cmu.edu Phone Number: --------------------- DATA & FILE OVERVIEW --------------------- # # Directory of Files in Dataset: List and define the different # files included in the dataset. This serves as its table of # contents. # Directory of Files: A. Filename: Obsidian Short description: A copy of the Obsidian GitHub repository. B. Filename: Obsidian tutorial.pdf Short description: A PDF version of the tutorial that Obsidian participants used. C. Filename: obsidian-guide Short description: The Obsidian manual, in HTML format. D. Filename: obsidian-tasks Short description: Starter code that the participants used in the Obsidian condition. E. Filename: Obsidian-tutorial.qsf Short description: The original Qualtrics tutorial instrument for Obsidian. F. Filename: Participant-data Short description: The code written by the participants. G. Filename: Post-study data, raw.csv Short description: The data entered by the participants in the post-study survey. H. Filename: Prescreen-anonymized.pdf Short description: The prescreening instrument we used to screen potential participants, with author information removed. I. Filename: Replication instructions.pdf Short description: Instructions to follow to configure a machine to run the experiment. E. Filename: Solidity-tutorial.pdf Short description: A PDF version of the tutorial that Solidity participants used. E. Filename: solidity-guide Short description: A Solidity manual, used by the Solidity participants to learn Solidity. E. Filename: solidity-tasks Short description: Starter code that the participants used in the Solidity condition. E. Filename: Solidity-tutorial.qsf Short description: The original Qualtrics tutorial instrument for Solidity. Additional Notes on File Relationships, Context, or Content (for example, if a user wants to reuse and/or cite your data, what information would you want them to know?): # # File Naming Convention: Define your File Naming Convention # (FNC), the framework used for naming your files systematically # to describe what they contain, which could be combined with the # Directory of Files. # File Naming Convention: N/A # # Data Description: A data description, dictionary, or codebook # defines the variables and abbreviations used in a dataset. This # information can be included in the README file, in a separate # file, or as part of the data file. If it is in a separate file # or in the data file, explain where this information is located # and ensure that it is accessible without specialized software. # (We recommend using plain text files or tabular plain text CSV # files exported from spreadsheet software.) # ----------------------------------------- DATA DESCRIPTION FOR: [FILENAME] ----------------------------------------- 1. Number of variables: 2. Number of cases/rows: 3. Missing data codes: Code/symbol Definition Code/symbol Definition 4. Variable List # # Example. Name: Gender # Description: Gender of respondent # 1 = Male # 2 = Female # 3 = Transgender # 4 = Nonbinary # 5 = Other gender not listed # 6 = Prefer not to answer # A. Name: Description: Value labels if appropriate B. Name: Description: Value labels if appropriate -------------------------- METHODOLOGICAL INFORMATION -------------------------- # # Software: If specialized software(s) generated your data or # are necessary to interpret it, please provide for each (if # applicable): software name, version, system requirements, # and developer. #If you developed the software, please provide (if applicable): #A copy of the software’s binary executable compatible with the system requirements described above. #A source snapshot or distribution if the source code is not stored in a publicly available online repository. #All software source components, including pointers to source(s) for third-party components (if any) 1. Software-specific information: Name: Version: System Requirements: Open Source? (Y/N): (if available and applicable) Executable URL: Source Repository URL: Developer: Product URL: Software source components: Additional Notes(such as, will this software not run on certain operating systems?): # # Equipment: If specialized equipment generated your data, # please provide for each (if applicable): equipment name, # manufacturer, model, and calibration information. Be sure # to include specialized file format information in the data # dictionary. # 2. Equipment-specific information: Manufacturer: Model: (if applicable) Embedded Software / Firmware Name: Embedded Software / Firmware Version: Additional Notes: # # Dates of Data Collection: List the dates and/or times of # data collection. # 3. Date of data collection (single date, range, approximate date) :