From c18289d6256d4e41d4f2603e2f97d918e31f89a4 Mon Sep 17 00:00:00 2001 From: Peter Zhu Date: Wed, 26 Sep 2018 03:42:59 +0000 Subject: [PATCH 01/11] GitBook: [2.0.0] 29 pages modified --- README.md | 26 ++ SUMMARY.md | 40 +++ comments/commentcontributorguide.md | 65 +++++ comments/commentstylecitation/README.md | 105 ++++++++ comments/commentstylecitation/citations.md | 2 + comments/commentstylecitation/commas.md | 2 + comments/commentstylecitation/quotations.md | 2 + comments/commentstylecitation/requirements.md | 2 + comments/commentstylecitation/style.md | 2 + comments/commentstylecitation/symbols.md | 2 + notes/notecontributorguide.md | 130 ++++++++++ notes/noteeditorguide.md | 82 ++++++ notes/notestylecitation/README.md | 45 ++++ notes/notestylecitation/citations.md | 2 + notes/notestylecitation/commas.md | 2 + notes/notestylecitation/organization.md | 2 + notes/notestylecitation/requirements.md | 2 + notes/notestylecitation/style.md | 2 + notes/notestylecitation/symbols.md | 2 + reports/reportcontributorguide.md | 220 ++++++++++++++++ reports/reporteditorguide.md | 41 +++ reports/reportstylecitation/README.md | 243 ++++++++++++++++++ reports/reportstylecitation/citations.md | 2 + reports/reportstylecitation/commas.md | 2 + reports/reportstylecitation/quotations.md | 2 + reports/reportstylecitation/requirements.md | 2 + reports/reportstylecitation/style.md | 2 + reports/reportstylecitation/substance.md | 2 + reports/reportstylecitation/symbols.md | 2 + 29 files changed, 1035 insertions(+) create mode 100644 SUMMARY.md create mode 100644 comments/commentcontributorguide.md create mode 100644 comments/commentstylecitation/README.md create mode 100644 comments/commentstylecitation/citations.md create mode 100644 comments/commentstylecitation/commas.md create mode 100644 comments/commentstylecitation/quotations.md create mode 100644 comments/commentstylecitation/requirements.md create mode 100644 comments/commentstylecitation/style.md create mode 100644 comments/commentstylecitation/symbols.md create mode 100644 notes/notecontributorguide.md create mode 100644 notes/noteeditorguide.md create mode 100644 notes/notestylecitation/README.md create mode 100644 notes/notestylecitation/citations.md create mode 100644 notes/notestylecitation/commas.md create mode 100644 notes/notestylecitation/organization.md create mode 100644 notes/notestylecitation/requirements.md create mode 100644 notes/notestylecitation/style.md create mode 100644 notes/notestylecitation/symbols.md create mode 100644 reports/reportcontributorguide.md create mode 100644 reports/reporteditorguide.md create mode 100644 reports/reportstylecitation/README.md create mode 100644 reports/reportstylecitation/citations.md create mode 100644 reports/reportstylecitation/commas.md create mode 100644 reports/reportstylecitation/quotations.md create mode 100644 reports/reportstylecitation/requirements.md create mode 100644 reports/reportstylecitation/style.md create mode 100644 reports/reportstylecitation/substance.md create mode 100644 reports/reportstylecitation/symbols.md diff --git a/README.md b/README.md index e69de29..ff8dfe4 100644 --- a/README.md +++ b/README.md @@ -0,0 +1,26 @@ +# FAQ + +## What is JOLT _Digest_? + +The [_JOLT Digest_](http://jolt.law.harvard.edu/digest) is the online companion to the Harvard Journal of Law & Technology \([JOLT](http://jolt.law.harvard.edu/)\). It is intended to serve as a one-stop source of legal news to professors, practitioners, law students, and the general public on issues at the intersection of law and technology. + +The Digest features short articles on new, precedential, or interesting cases; new legislation; administrative developments of note; and other interesting happenings. By applying JOLT’s traditionally high editing standards to the Digest, we create a uniquely useful and trustworthy resource. + +## Do you conform with the Oxford Comma? + +Yes. Read more [here](reports/reportstylecitation/#commas). + +## Meet the editing team! + +**Contributors** write the Report articles for _JOLT Digest_ and also suggest sources of online commentary that can be linked from Digest articles. + +**Report Editors** supervise the Contributors. Report Editors are responsible for editing article drafts and adding additional relevant materials. + +**Subject Matter Coordinators** \(Mindy Nam and Stella Mao\) assign topics to Contributors and Report Editors on their subject matter teams. Assignments include the topic and links to sources that help Contributors to understand the issue and links to relevant online commentary. + +**Digest Content Editors** \(Brian Kulp and Phillip Takhar\) take the lead on seeing Digest Student Notes and Comments from submission to publication. This involves back-and-forth on substantive edits with the authors to make sure their pieces meet Digest standards. + +**Digest Submissions Editor** \(Wendy Chu\) oversees and assists the Coordinators to generate topics and schedule assignments, coordinates the assignment process, provides a final layer of editing for entries, upload posts into WordPress, and ensure that the entries remain up-to-date as new developments occur. + +**Digest Executive Editor** \(Peter Zhu\) supervises the Digest Content Editor and other Digest team members, creates the Digest publication schedule, and provides an additional layer of editing for entries. + diff --git a/SUMMARY.md b/SUMMARY.md new file mode 100644 index 0000000..b4f4722 --- /dev/null +++ b/SUMMARY.md @@ -0,0 +1,40 @@ +# Table of contents + +* [FAQ](README.md) + +## Reports + +* [Contributor's Guide](reports/reportcontributorguide.md) +* [Editor's Guide](reports/reporteditorguide.md) +* [Style & Citations Guide](reports/reportstylecitation/README.md) + * [Requirements](reports/reportstylecitation/requirements.md) + * [Style](reports/reportstylecitation/style.md) + * [Commas](reports/reportstylecitation/commas.md) + * [Symbols](reports/reportstylecitation/symbols.md) + * [Quotations](reports/reportstylecitation/quotations.md) + * [Citations](reports/reportstylecitation/citations.md) + * [Substance](reports/reportstylecitation/substance.md) + +## Notes + +* [Contributor's Guide](notes/notecontributorguide.md) +* [Editor's Guide](notes/noteeditorguide.md) +* [Style & Citations Guide](notes/notestylecitation/README.md) + * [Requirements](notes/notestylecitation/requirements.md) + * [Organization](notes/notestylecitation/organization.md) + * [Citations](notes/notestylecitation/citations.md) + * [Style](notes/notestylecitation/style.md) + * [Commas](notes/notestylecitation/commas.md) + * [Symbols](notes/notestylecitation/symbols.md) + +## Comments + +* [Commentator's Guide](comments/commentcontributorguide.md) +* [Style & Citations Guide](comments/commentstylecitation/README.md) + * [Requirements](comments/commentstylecitation/requirements.md) + * [Style](comments/commentstylecitation/style.md) + * [Commas](comments/commentstylecitation/commas.md) + * [Symbols](comments/commentstylecitation/symbols.md) + * [Quotations](comments/commentstylecitation/quotations.md) + * [Citations](comments/commentstylecitation/citations.md) + diff --git a/comments/commentcontributorguide.md b/comments/commentcontributorguide.md new file mode 100644 index 0000000..e948bbf --- /dev/null +++ b/comments/commentcontributorguide.md @@ -0,0 +1,65 @@ +# Commentator's Guide + +## Welcome to the Commentator's Guide! + +The JOLT _Digest_ Commentary section is a new platform for professionals, academics, and students to participate in ongoing discussions about cutting-edge legal issues without the formality of our Notes or the impartiality of our Reports. By removing formalities such as Bluebooking citations, we hope that our Comments can bring forth critical insights and opinions in a timely manner. Indeed, drafting Comments should take at most one month from idea to publication! + +_Digest_ Comments are about 2,000 words and can come in several general forms: opinion pieces, primers, or responses. This guide will provide an overview of your responsibilities as the author of a _Digest_ Comment. + +## Writing Process in a Nutshell {#nutshell} + +The Commentary writing process can be broken down into the following steps. + +* [Step 1](commentcontributorguide.md#step1): Getting Started +* [Step 2](commentcontributorguide.md#step2): Drafting the Comment +* [Step 3](commentcontributorguide.md#step3): Digest Masthead Edits +* [Step 4](commentcontributorguide.md#step4): Finalizing the Comment + +## Step 1: Getting Started {#step1} + +You, the Comment author, are hoping to publish a Comment with JOLT _Digest_. Your first task is to come up with a topic. Because Comments should be timely and related to law and technology, you can run your topic by the Digest Executive Editor. However, you can also submit a draft without asking us beforehand. + +As mentioned in the introduction, Comments come in three forms: opinion pieces, primers, or responses. Below is a summary of each. + +### Opinion Pieces + +Opinion pieces are argumentative. They should clearly indicate the logical progression of the argument, rely on facts, and declare their assumptions. + +These Comments can generally be sorted into three types of arguments: + +1. Identifying a new problem; +2. Proposing a process to solve a problem; or +3. Advancing a specific solution to an identified problem + +If you feel that your piece does not fit cleanly within this description, that is fine. + +### Primers + +Primers should introduce individuals with no knowledge to the topic. They are not argumentative. Instead, primers offer a common language and understanding behind a dispute. For example, several primers might have stemmed from the FBI–Apple dispute: \(i\) introduction to encryption; \(ii\) introduction to iPhone security features; and \(iii\) introduction to the All Writs Act. + +A primer can also address several issues related to the topic. For example, you can write a Primer on the FBI-Apple dispute that covers each of the above topics. + +### Responses + +Response pieces must reply to a JOLT publication. We strongly favor responses to articles published in our print edition. Authors should clearly identify the contested article, acknowledge where they agree with the JOLT publication and where they disagree. JOLT _Digest_ will inform the author of the contested article that a response is being drafted so that he or she has the option to draft a rebuttal. + +## Step 2: Drafting the Comment {#step2} + +If seeking our approval for your topic, you must send us a draft within two \(2\) weeks of receiving our confirmation. The Comment must be consistent with the [Digest Commentary Style Guide](commentstylecitation/). + +The final Comment should be around 2,000 words in length. Because Digest’s readership varies in terms of familiarity, you should assume the reader knows very little about the chosen subject. Comments should thus include a brief introduction to the problem, explain why the topic is important, and provide links to foundational knowledge. + +You may include a short biography at the end of the Comment, as well as links to your social media accounts. + +## Step 3: Digest Masthead Edits {#step3} + +Please send your completed draft to the Digest Executive Editor \(currently Filippo Raso\). The Digest Executive Editor will review the Comment for factual accuracy, compliance with the style guide, and organization. The Digest Executive Editor will only reject claims that are patently untrue, though he may request additional sources to establish the validity of a claim. + +## Step 4: Finalizing the Comment {#step4} + +The Digest Executive Editor will return the Comment to you for your final review. Please address his comments. With your approval, he will post the final article on the Digest Commentary page. + +## Thank You! + +The JOLT _Digest_ team thanks you for the time you will be putting into creating Digest content. Please feel free to email the Digest Masthead if you have any concerns or suggestions on improving the process! + diff --git a/comments/commentstylecitation/README.md b/comments/commentstylecitation/README.md new file mode 100644 index 0000000..0360621 --- /dev/null +++ b/comments/commentstylecitation/README.md @@ -0,0 +1,105 @@ +# Style & Citations Guide + +## Welcome to the Comment Style and Citation Guide! + +Authors should review the Style and Citation Guide before they begin drafting their Comment. + +## Requirements {#requirements} + +All Comments should hyperlink to the original source material, preferably a PDF \(e.g., court opinion or filing, legislation. Points should generally be well supported and should link to related content whenever possible. + +## Style {#style} + +As an online program, Digest Comments have unique formatting requirements distinct from other legal journal writings. Below are some common items to check: + +* Add only one space between sentences. +* Add Quotation marks around acronyms located in parentheticals, e.g. Digital Millennium Copyright Act of 1998 \(“DMCA”\). +* Do not include spaces around an em dash \(“—“\). +* Do not capitalize mid-sentence generic party names: plaintiff, defendant, appellee, and appellant +* Do not hyphenate the following words: decisionmaker, factfinder +* Italicize or bold for emphasis, as underlines look like a broken link. + +## Commas {#commas} + +When listing three or more things, separate each pair with a comma, including the last pair. The last comma precedes the coordinating conjunction \(e.g. _and_ or _or_\). + +> **Example:** Lions, tigers, and bears. + +## Symbols {#symbols} + +Outside of citations, do not use "§" and "¶." Instead, always spell out and capitalize "Section" and "Paragraphs" in place of symbols. + +## Quotations {#quotations} + +**Avoid block quotations to the extent possible.** You should be linking to sources, so there’s no need to quote in length. The exception to this rule, though, is the situation when you are analyzing statutory language; in that case, having the statute conveniently displayed in the body of the article is encouraged. + +## Citations {#citations} + +_Digest_ Comments need not follow Bluebook citation format. Indeed, you should cite sources primarily through hyperlink. Please archive your links to prevent linking to sources that later become unavailable. The Editing Team can also help out with this during the editing process. Please use \(recommended\) or to archive your links. + +Original sources are always preferred over secondary sources or other reports. + +### Online News Sources + +Support your statements that derive from online news sources by creating hyperlinks out of parts of the statement. Select which words should be hyperlinked in the following preference. + +1. Name of the blog, newspaper, website +2. Name of the author +3. Operative phrase when the statement does not contain either \(1\) or \(2\) + +> **Example:** [Ars Technica](https://arstechnica.com/tech-policy/2009/04/google-loses-on-appeal-will-face-adwords-trademark-suit/) provides commentary. +> **Not:** Ars Technica [provides](https://arstechnica.com/tech-policy/2009/04/google-loses-on-appeal-will-face-adwords-trademark-suit/) commentary. + +Generally, a blog’s name is preferred over the author; however, the author’s name may be included as desired. If it is a personal blog bearing the name of the sole contributor to the blog, the name of the author may be used. + +> **Example:** [Eric Posner](http://ericposner.com/what-has-been-the-effect-of-the-convention-against-torture/) provides commentary. +> **Example:** Stewart Baker on [The Volokh Conspiracy](http://www.volokh.com/2014/01/01/obama-administration-dominates-2014-awards-dubious-achievements-privacy-law/) reviews the Privies. + +Where it is awkward or undesirable to name the source in the sentence, create a hyperlink out of the group of words that the source best supports. Finding the right group of words can be a bit of an art, so work with your Editor on this. + +> **Example:** In May 2009, [the European Commission fined Intel](http://ec.europa.eu/competition/sectors/ICT/intel.html) a record 1.06 billion Euros for abusing its dominant market position. +> **Example:** While prosecution [placed significant emphasis](https://www.nytimes.com/2017/06/06/us/suicide-texting-manslaughter-trial.html) on the text messages between the Carter and Roy during the trial, focusing particularly on the fact that their relationship was so tied to online communication, the judge rested his conclusion on a phone call they exchanged shortly before Roy’s suicide. +> **Not:** While prosecution placed significant [emphasis](https://www.nytimes.com/2017/06/06/us/suicide-texting-manslaughter-trial.html) on the text messages between the Carter and Roy during the trial, focusing particularly on the fact that their relationship was so tied to online communication, the judge rested his conclusion on a phone call they exchanged shortly before Roy’s suicide. + +### Law Review Articles + +In-text citations to law review articles need not be in Bluebook format, but should indicate the name of the author\(s\) and link to a PDF of the article. As with online news sources, hyperlink the name of the source where possible, but put the link on a descriptive phrase otherwise. + +> **Example:** The Innovator’s Patent Agreement bears similarities to the [defensive patent license \(“DPL”\) proposed](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2040945) by Jason Schultz and Jennifer Urban. + +### Statutes + +If a statute is available through an open access online source, such as through the Cornell Legal Information Institute, hyperlink to the source in text, and then Bluebook the source when it is cited. When referring to an act generally, cite to the first U.S.C. section of the Act. When referring to a particular provision of an act for the first time, include a hyperlink to that provision. The hyperlinked text should be the location in the United States Code. + +Make sure to spell out the official name of the act the first time it is cited. + +> **Example:** [Visual Artists Rights Act of 1990](http://www.law.cornell.edu/uscode/17/usc_sec_17_00000106---A000-.html) \(“VARA”\), 17 U.S.C. § 106A \(2012\), a U.S. law offering moral rights to visual artists, is similarly limited. +> **Example:** Section 2520 of the Wiretap Act of 1968 \(“Wiretap Act”\), [18 U.S.C. § 2520](https://www.law.cornell.edu/uscode/text/18/2520), provides a private right of action against persons who violate the provisions of Section 2511 of the Wiretap Act, [18 U.S.C. § 2511](https://www.law.cornell.edu/uscode/text/18/2511). + +### Cases & Court Documents + +Bluebook cases in full the first time they are cited and use an unambiguous shortened case name thereafter. Case names in the full cite should not be italicized if it is hyperlinked. For aesthetic purposes, do not include pincites throughout the article. + +> **Example:** [Fourco Glass Co. v. Transmirra Products Corp.](https://www.law.cornell.edu/supremecourt/text/353/222), 353 U.S. 222 \(1957\) +> **Example:** _Fourco Glass Co. v. Transmirra Products Corp._, 353 U.S. 222 \(1957\) +> **Not:** [_Fourco Glass Co. v. Transmirra Products Corp._](https://www.law.cornell.edu/supremecourt/text/353/222), 353 U.S. 222 \(1957\) + +Shortened case names should always be italicized and never hyperlinked. + +> **Example:** _Fourco Glass_ +> **Not:** Fourco Glass +> **Not:** [_Fourco Glass_](https://www.law.cornell.edu/supremecourt/text/353/222) + +However, procedural phrases like _In re_ should always be italicized, even if they are part of hyperlinks. + +Remember that, for purposes of short forms, a citation to a court document including a case citation suffices as a citation to the case itself \(Rule 10.8.3\). + +Since _Digest_ posts are often more recent than print articles, they often rely on pending cases, rule 10.8.\* Make sure to cite slip opinions \(rule 10.8.1\(b\)\) and cases decided en banc \(rule 10.6.1\) as appropriate. + +**Hosted By** -- If a PDF of a court document is available through an open access online source \(i.e., not through Westlaw or Lexis Nexis\), hyperlink to the source from the document type or, if none, case name in the Bluebook citation. If the PDF is hosted by a non-court source, include “hosted by” language with the hyperlink on the document type \(not a Bluebook abbreviation\). + +> **Example:** [MGA Entertainment, Inc. v. Mattel, Inc.](http://www.sunsteinlaw.com/media/BratzTCC.pdf), No. 09-55673 \(9th Cir. July 22, 2010\), hosted by sunsteinlaw.com. +> **Example:** Viacom International Inc. v. YouTube, Inc., No. 07 Civ. 2103 \(S.D.N.Y. June 23, 2010\), [slip opinion](http://docfiles.justia.com/cases/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf), hosted by Justia.com. +> **Example:** Complaint for Declaratory Judgment and Injunctive Relief, GoldieBlox, Inc. v. Island Def Jam Music Group, A Div. of UMG Recordings, Inc., No. 3:13-cv-05428 \(N.D. Cal. Nov. 21, 2013\), [complaint](http://www.scribd.com/doc/186402972/Beastie) hosted by Scribd. +> **Not:** Viacom Int’l Inc. v. YouTube, Inc., No. 07 Civ. 2103 \(S.D.N.Y. June 23, 2010\), [slip op.](https://cases.justia.com/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf) hosted by Justia.com + diff --git a/comments/commentstylecitation/citations.md b/comments/commentstylecitation/citations.md new file mode 100644 index 0000000..a8c4def --- /dev/null +++ b/comments/commentstylecitation/citations.md @@ -0,0 +1,2 @@ +# Citations + diff --git a/comments/commentstylecitation/commas.md b/comments/commentstylecitation/commas.md new file mode 100644 index 0000000..97a8b97 --- /dev/null +++ b/comments/commentstylecitation/commas.md @@ -0,0 +1,2 @@ +# Commas + diff --git a/comments/commentstylecitation/quotations.md b/comments/commentstylecitation/quotations.md new file mode 100644 index 0000000..ef84a78 --- /dev/null +++ b/comments/commentstylecitation/quotations.md @@ -0,0 +1,2 @@ +# Quotations + diff --git a/comments/commentstylecitation/requirements.md b/comments/commentstylecitation/requirements.md new file mode 100644 index 0000000..c4a55bf --- /dev/null +++ b/comments/commentstylecitation/requirements.md @@ -0,0 +1,2 @@ +# Requirements + diff --git a/comments/commentstylecitation/style.md b/comments/commentstylecitation/style.md new file mode 100644 index 0000000..dec0061 --- /dev/null +++ b/comments/commentstylecitation/style.md @@ -0,0 +1,2 @@ +# Style + diff --git a/comments/commentstylecitation/symbols.md b/comments/commentstylecitation/symbols.md new file mode 100644 index 0000000..9a0ef51 --- /dev/null +++ b/comments/commentstylecitation/symbols.md @@ -0,0 +1,2 @@ +# Symbols + diff --git a/notes/notecontributorguide.md b/notes/notecontributorguide.md new file mode 100644 index 0000000..ec88033 --- /dev/null +++ b/notes/notecontributorguide.md @@ -0,0 +1,130 @@ +# Contributor's Guide + +## Welcome to the Note Contributor's Guide! + +A _Digest_ Note proffers a **novel analysis** on an issue related to law and technology. It contributes something new and interesting to the field. While a Note may include economic, cultural, or other types of arguments, it must revolve around the law. + +You should make sure that your Note idea is not preempted; do some background research and work with your Note Editor on refining the idea. + +**Your Tasks** 1. Come up with a **novel analysis** related to law and technology. 2. Provide an outline. 3. Write a 1500-2000 word analysis piece on the topic. + +1. Respond to suggestions from the [Note Editor](noteeditorguide.md). + +## Requirements {#requirements} + +### Novelty + +Your Note should put forth your analysis of a particular area of law and technology. While you should write about a novel idea, you need not canvas all of current literature in making sure your idea was not preempted. Your idea will be fine to write about if an on-point piece does not show in the first page of a google search or first five links of a search on secondary materials on Westlaw or LexisNexis. + +Possible topics include + +* Inconsistencies within a recent opinion +* Inconsistencies within a line of opinions +* The dissenting opinion got it right +* The majority opinion got it right but for a different reason +* Unforeseen consequences of a recent case +* Critiques of a law review article +* And so on... + +### Length + +Your Note should be within 1500-2000 words. You may go over 2000 words but only if both you and your Note Editor agree that your thesis requries the extra space. Every Note will have an objective portion, that sets up the context of your piece, and a subjective portion, that lays out your argument. There is no required distribution of words between the two portions -- the only requirement is that there is a subjective portion. + +Citations will not count towards the word limit. + +### Citations + +Notes are more formal pieces than [_Digest_ Reports](../reports/reportcontributorguide.md). And so, you will need to provide pincites for every statement you attribute to someone else. **Follow the Bluebook whitepages subject to the rules laid out in the** [**Notes Style and Citation Guide**](notestylecitation/)**.** When submitting drafts, provide citations in endnotes rather than footnotes. + +## Logistics + +You will be working closely with your Note Editor throughout the process leading to publishing. Submit drafts to your Editor via email. Follow the guidelines below when formatting your email. + +### Email Subject + +Please use the following template for your subject lines + +> \[JOLT Digest\] `contributor_name` Note `draft_version` +> **Example:** \[JOLT Digest\] Fishwick Note Outline +> **Example:** \[JOLT Digest\] Fishwick Note First Draft +> **Example:** \[JOLT Digest\] Fishwick Note Second Draft + +### Document Naming + +Please submit drafts as either .doc or .docx files. Label drafts in the following manner: + +> `contributor_name` `draft_version` `date_emailed` +> **Example:** Fishwick First Draft 2017-06-30.doc + +## Writing Process in a Nutshell {#nutshell} + +The process can be broken down into the following steps. + +1. [Outline/Rough Draft](notecontributorguide.md#outline) +2. [First Draft](notecontributorguide.md#first) +3. [Second Draft](notecontributorguide.md#second) +4. [Submission](notecontributorguide.md#submission) + +## Outline/Rough Draft {#outline} + +This is an opportunity for the Note Editor to provide feedback on the Note in the early stages of writing it, so that you can tailor, structure, and address issues. The outline/draft should be more than the proposal, and should reflect some research, but it needn’t be a complete article. The Note Editor should be available in case you have questions or would like help with the direction of the Note. + +There may be multiple back-and-forths with the Note Editor on the outline. This is ok: you want to minimize the number of major substantive edits once you start writing. + +## First Draft {#first} + +**Your Tasks** + +1. Submit your completed draft over email. +2. Note Editor will spend one week editing. +3. Note Editor will return your track-changed draft with comments via email. + +Send your completed first draft to + +* Your Note Editor +* Submissions Editor \(cc\) +* joltdigest@mail.law.harvard.edu \(cc\) + +The Note Editor should spend up to **one week** reviewing the Note. The Editor will do the following. + +* provide local substantive suggestions in the margins \(through comments\) +* provide general substantive suggestions at the end of the piece +* correct grammatical errors in-text \(through track-change feature in Microsoft Word\) or through the comment feature +* verify citations + +After these changes are made, the Note Editor will email the edited document to you and CC both \[Submissions Editor email\] and joltdigest@mail.law.harvard.edu. Try to meet with the Note Editor in person or over the phone to discuss the Note and the changes he or she made. + +If at any point the Note Editor has a question or concern regarding the Note or needs someone to review part of the Note, he or she should feel free to email the Submissions Editor at \[Submissions Editor email\]. + +In between the first and second drafts, feel free to reach out to the Note Editor for any substantive or grammatical questions. The editing process for the second draft should adhere to the same guidelines as the editing process for the first draft. By the time the second draft is formally submitted, the Note should be organized and coherent. Most if not all sources should be found. + +## Second Draft {#second} + +**Your Tasks** + +1. Evaluate your Note Editor's feedback and make changes accordingly. +2. Submit your revised draft over email. +3. Be available to field editing requests from your Note Editor. + +Send your completed second draft to + +* Your Note Editor +* Submissions Editor \(cc\) +* joltdigest@mail.law.harvard.edu \(cc\) + +The next step after your Note Editor receives your second draft depends on what changes to the Note are needed. + +If all the necessary changes are grammatical and there are only very minor substantive changes, the Note Editor will direct you to make those changes. + +If the Note requires substantial change, the Note Editor should email \[Submissions Editor email\] and joltdigest@mail.law.harvard.edu a copy of the Note and a description of these proposed major changes. The Digest Masthead will look at the Note and determine whether these major changes can be made in time for publication or if publication of the Note’s publication needs to be delayed. You should be working closely with the Note Editor throughout the editing process so that substantive changes will not be necessary at this point. + +## Submission {#submission} + +After both you and your Note Editor agree on the final draft, the Note Editor will email this finalized draft to + +* You, the Contributor +* Submissions Editor +* joltdigest@mail.law.harvard.edu + +You will be notified when your Note is published. Be sure to look it over for any mistakes. + diff --git a/notes/noteeditorguide.md b/notes/noteeditorguide.md new file mode 100644 index 0000000..76d947d --- /dev/null +++ b/notes/noteeditorguide.md @@ -0,0 +1,82 @@ +# Editor's Guide + +## Welcome to the Note Editor's Guide! + +A _Digest_ Note proffers a thesis that advances a **novel analysis** on an issue related to law and technology. It contributes something new and interesting to the field. While a Note may include economic, cultural, or other types of arguments, it must revolve around the law. + +**Your Tasks** 1. Check that the [Note Contributor](notecontributorguide.md)'s idea is novel. 2. Provide grammatical and substantive suggestions to the Contributor's outline and drafts. 3. Verify both the technical and substantive accuracy of citations. + +1. Submit the final draft to the Submissions Editor. + +## Getting Started + +Try to meet with the Contributor at least once in person or over the phone to discuss your game plan for writing and editing the Note. The Contributor should explain his or her vision, where the most help will be needed, scheduling constraints, etc. You and the Contributor will work closely from submission through final edits. + +## Requirements + +You will help the Contributor meet the [requirements](notecontributorguide.md#requirements) expected of a _Digest_ Note. In short, you should + +* help make sure the Contributor's idea is not preempted by a quick internet search +* ensure the Contributor is keeping within the word-limit. +* discuss with the Contributor if more space is needed. +* review for substantive and grammatical errors. +* ensure accurate citations. + +## Editing Process in a Nutshell {#nutshell} + +The process can be broken down into the following steps. + +1. [Outline/Rough Draft](noteeditorguide.md#outline) +2. [First Draft](noteeditorguide.md#first) +3. [Second Draft](noteeditorguide.md#second) +4. [Submission](noteeditorguide.md#submission) + +## Outline/Rough Draft {#outline} + +After proposing a writing topic, the Contributor will email an outline for you to review. While the outline should be more than the initial proposal---reflecting some research---it need not be a complete draft. + +Aim to provide substantive feedback on the outline before the Contributor starts writing. In particular, make sure + +* the topic reflects more than just summarizing cases or other's opinions. +* the content can fit within the word-limit. +* organization of the Note is coherent. +* sources are valid and not overturned. + +You should be available to field the Contributor's questions throughout the process but especially in the beginning. There may be multiple iterations of the outline. Focus on the substance and aim to minimize the number of major substantive edits you and the Contributor will have to make on the drafts. + +## First Draft {#first} + +The Contributor will email you the first draft in a Microsoft Word Document format. You will have **one week** to review the Note. You should + +* provide local substantive suggestions in the margins \(through comments\) +* provide general substantive suggestions at the end of the piece +* correct grammatical errors in-text \(through track-change feature in Microsoft Word\) or through the comment feature +* verify citations + +Name the marked-up draft document in the following manner. + +> `contributor_name` `draft_version` `date_emailed`\_`initials`edits.doc +> **Examples:** Fishwick First Draft 2017-06-30\_svedits.doc + +Afterwards, email the marked-up draft to the Contributor and CC the \[Submissions Editor\] and joltdigest@mail.law.harvard.edu. + +## Second Draft {#second} + +In between the first and second drafts, you should be available to the Contributor for any substantive or grammatical questions. The editing process for the second draft should adhere to the same guidelines as that for the first draft. By the time the second draft is formally submitted, the Note should be organized and coherent. + +The Contributor should email the second draft to you and CC \[Submissions Editor\] and joltdigest@mail.law.harvard.edu. Forward the email to these parties if the Contributor fails to include them. + +Once you receives the second draft, your next step is dependent on what changes need to be made to the Note. If all the necessary changes are grammatical and there are only very minor substantive changes, direct the Contributor to make those changes and email back the final version of the Note. + +If major substantive changes need to be made to the Note at this point, you should email the \[Submissions Editor\] and joltdigest@mail.law.harvard.edu a copy of the Note and a description of these proposed major changes. The _Digest_ Masthead will look at the Note and determine whether these major changes can be made in time for publication or if publication of the Note’s publication needs to be delayed. + +## Submission {#submission} + +Once you and the Contributor agree on the final draft, email it to + +* the Contributor +* Submissions Editor +* joltdigest@mail.law.harvard.edu + +You will be notified when your Note is published. Be sure to look it over for any mistakes. + diff --git a/notes/notestylecitation/README.md b/notes/notestylecitation/README.md new file mode 100644 index 0000000..add6f34 --- /dev/null +++ b/notes/notestylecitation/README.md @@ -0,0 +1,45 @@ +# Style & Citations Guide + +## Welcome to the Note Style and Citation Guide! + +_Digest_ Notes are JOLT Student Notes adapted for the online medium. This means you will need to follow the style and citation rigor expected in a Law Journal Note, subject to a few adaptions for it being posted online. + +## Requirements {#req} + +Follow The Bluebook \(20th Edition\) whitepages where its rules do not directly conflict with the rules laid out here. + +## Organization {#org} + +Use section headings to separate your Note into digestable parts. Do not precede your section headings with any counters \(e.g. Roman Numerals, Arabic Numerals, Letters, etc.\). Do not use subsections. + +## Citations {#citations} + +Provide a citation for every statement that is not your original idea. + +As _Digest_ Notes are not paginated, do not use footnotes. Your citations will, instead, be in endnotes. In citations, use _italics_ instead of underlines and normal font instead of small-caps. + +But keep in mind that Readers will rarely refer to endnotes. As such, try to tailor endnotes to contain only citations. To convey helpful but nonessential information, consider placing them in in-text parentheticals or cutting them out entirely. + +## Style {#style} + +Since Digest is available online, some formatting preferences may be different, so this Digest citation guide supersedes the generic JOLT Style Guide. Below are some common items to check: + +* Only one space between sentences. +* Do not include spaces around an em dash \(“—“\) +* Quotation marks around acronyms located in parentheticals, e.g. Digital Millennium Copyright Act of 1998 \(“DMCA”\) +* Do not capitalize the following party names: plaintiff, defendant, appellee, and appellant +* Do not hyphenate the following words: decisionmaker, factfinder + +There are also some additional requirements specific to a _Digest_ Note: + +* Use only _italics_ for formatting emphasis \(not bold or underline\). +* Do not use small-caps. + +## Commas {#commas} + +Use the serial comma. Read [here](../../reports/reportstylecitation/#commas) for more information. + +## Symbols {#symbols} + +Outside of citations, do not use "§" and "¶." Instead, always spell out and capitalize "Section" and "Paragraphs" in place of symbols. + diff --git a/notes/notestylecitation/citations.md b/notes/notestylecitation/citations.md new file mode 100644 index 0000000..a8c4def --- /dev/null +++ b/notes/notestylecitation/citations.md @@ -0,0 +1,2 @@ +# Citations + diff --git a/notes/notestylecitation/commas.md b/notes/notestylecitation/commas.md new file mode 100644 index 0000000..97a8b97 --- /dev/null +++ b/notes/notestylecitation/commas.md @@ -0,0 +1,2 @@ +# Commas + diff --git a/notes/notestylecitation/organization.md b/notes/notestylecitation/organization.md new file mode 100644 index 0000000..c3aae8d --- /dev/null +++ b/notes/notestylecitation/organization.md @@ -0,0 +1,2 @@ +# Organization + diff --git a/notes/notestylecitation/requirements.md b/notes/notestylecitation/requirements.md new file mode 100644 index 0000000..c4a55bf --- /dev/null +++ b/notes/notestylecitation/requirements.md @@ -0,0 +1,2 @@ +# Requirements + diff --git a/notes/notestylecitation/style.md b/notes/notestylecitation/style.md new file mode 100644 index 0000000..dec0061 --- /dev/null +++ b/notes/notestylecitation/style.md @@ -0,0 +1,2 @@ +# Style + diff --git a/notes/notestylecitation/symbols.md b/notes/notestylecitation/symbols.md new file mode 100644 index 0000000..9a0ef51 --- /dev/null +++ b/notes/notestylecitation/symbols.md @@ -0,0 +1,2 @@ +# Symbols + diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md new file mode 100644 index 0000000..4a901dd --- /dev/null +++ b/reports/reportcontributorguide.md @@ -0,0 +1,220 @@ +# Contributor's Guide + +## Welcome to the Report Contributor's Guide! + +This guide will provide an overview of your responsibilities as a **Contributor** of a _**Digest**_ **Report**. Reports are short objective overviews, 500-700 words in length, of recent court opinions or pieces of legislation. They also provide links to primary sources and additional commentary for readers who want to dig deeper. + +Subject Matter Coordinators \(SMCs\) are constantly looking for cutting edge developments in law & technology. They will assign the topic to you and an Report Editor. Your job is to write the substantive content of the report while the Report Editor will help you ensure it is publication-ready. + +{% hint style="info" %} +### Writing Process in a Nutshell + +* [Step 1](reportcontributorguide.md#step1): Getting Started +* [Step 2](reportcontributorguide.md#step2): Receiving and Confirming Receipt of Your Assignment +* [Step 3](reportcontributorguide.md#step3): Drafting the Report +* [Step 4](reportcontributorguide.md#step4): Forwarding the Report & Following Up +{% endhint %} + +Unless otherwise noted, all of the following communications are designed to \(and should\) occur via email. + +## Step 1: Getting Started {#step1} + +You, the _Digest_ Contributor, will be assigned reports according to the availability and subject matter preferences you submitted in the sign-up survey. SMCs will simultaneously assign Report Editors and Contributors to a topic. Unless your Coordinator specified otherwise, you will have **four days** to finish a draft. + +If you are unable to complete an assignment, please notify the assigning SMC immediately. If your availability changes during the year, notify the Digest Executive Editor. + +## Step 2: Receiving and Confirming Receipt of Your Assignment + +{% tabs %} +{% tab title="Instructions" %} +The SMC will send you and the Report Editor an assigning email with: + +1. Name of your Contributor and Editor +2. Draft due date +3. Report topic + 1. Background \(parties, procedural posture, etc.\) + 2. Significance of the case/legislation + 3. Link or attachment to primary source +4. Link to [Contributor](reportcontributorguide.md#welcome-to-the-report-contributors-guide), [Editor](reporteditorguide.md#welcome-to-the-report-editors-guide), and [Style & Citation Guide](reportstylecitation/) +5. Credentials for online Bluebook access + +If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Executive Editor, who are also available to answer questions. +{% endtab %} + +{% tab title="Sample Email" %} +#### ACTION + +Please reply all to this email and confirm that you are able to take on this week's Digest assignment. + +#### SUMMARY + +**Assignment Date:** February 17, 2018 + +**Assignment:** summarize Aatrix Software, Inc. v. Green Shades Software, Inc., No. 2017-1452, 2018 WL 843288 \(Fed. Cir. Feb. 14, 2018\) along with links to at least two outside sources. You can find examples of posts at [https://jolt.law.harvard.edu/digest/category/?cat=patent](https://jolt.law.harvard.edu/digest/category/?cat=patent). + +**Draft Deadline** \(Contributor send draft to me and Editor\): 11:59 p.m. Wed, Feb 21. + +**Edits Deadline** \(Editor send marked up draft to me and Contributor\): 11:59 p.m. Sat, Feb 24. + +Thanks for writing for Digest this semester! According to the Fall 2017 Report Schedule, <**Contributor**>, you have been assigned the role of Digest Contributor for this week. **<Editor>**, you are assigned the role or Report Editor. + +**ASSIGNMENT** +<**Contributor>**, your task is to summarize Aatrix Software, Inc. v. Green Shades Software, Inc., No. 2017-1452, 2018 WL 843288 \(Fed. Cir. Feb. 14, 2018\). + +At issue here is whether the patented technology should have been patent-eligible. 35 U.S.C. § 101 defines what may be patented. Courts have consistently held that abstract ideas, laws of nature, and natural phenonmenons are not patentable. The question then often turns on what falls in each of these three categories. Though commonplace, the issue is probably the most fundamental question in patent law and supported by one of the least defined doctrines in the field. + +You will almost certainly come across the Alice test. Courts applying the test engage in a two-step inquiry. In step one, courts figure out whether the matter at issue falls in one of the three patent-ineligible categories: abstract idea, laws of nature, or natural phenomenon. If not, then it is patentable. If so, then the courts ask whether there is an "inventive concept" that "transforms" the patent-ineligible matter into something "more" that is patentable. Readers will be most curious about the facts the courts considered in reaching their decisions on each of these steps. + +**<Editor>**, your job is to ensure the report is substantively accurate and give suggestions on big picture flow. Defer to the Contributor on writing style. + +This can be a very confusing case so don't hesitate to email me with any questions. +You'll find the case at [http://www.cafc.uscourts.gov/sites/default/files/opinions-orders/17-1452.Opinion.2-12-2018.1.PDF](http://www.cafc.uscourts.gov/sites/default/files/opinions-orders/17-1452.Opinion.2-12-2018.1.PDF) \(also attached\). You can find other Federal Circuit cases at [http://www.cafc.uscourts.gov/opinions-orders/search/report.html](http://www.cafc.uscourts.gov/opinions-orders/search/report.html). + +In addition to summarizing the case, your article should also include at least 2 hyperlinks to related material and/or commentary. These can include briefs \(filed by the party or amicus\), legal blogs, JOLT articles or Digest posts, news articles. + +You can find an example of a Digests post [here](http://jolt.law.harvard.edu/digest/two-way-media-v-comcast). + +You should follow the appropriate Digest Report guides: [Style & Citations Guide](reportstylecitation/), [Contributor's Guide](reportcontributorguide.md), and [Editor's Guide](reporteditorguide.md). On occasion, the Style Guide requires you to follow the Bluebook \(though we never pincite\). JOLT maintains several online bluebook accounts to help with that process. Log-in with the following credentials at [www.legalbluebook.com](http://www.legalbluebook.com/). + +Accounts: \[excluded\] + +Password: \[excluded\] + +**<Contributor>**, please send **<Editor>** and me your draft by 11:59pm Wed, Feb 21. **<Editor>**, please send the marked up draft to **<Contributor>** and me by 11:59pm Sat, Feb 24. Requirements are listed in your corresponding guides. Please follow them closely. + +Lastly, Digest is looking to constantly improve the publication process. If you find any part of it confusion -- the requirements, guides, communication, etc. -- please let us know so that we can make adjustments. +{% endtab %} +{% endtabs %} + +{% hint style="success" %} +#### Your Responsibilities + +After receiving your assignment from the Subject Matter Coordinator \(SMC\), immediately "reply all" to the email and: + +1. Confirm to the Coordinator and Editor that you have received and can complete the assignment. +2. Alert the Coordinator and Editor to any problems that may delay your submission +{% endhint %} + +If you simply cannot write the report within the required time, please let the SMC know as soon as possible so the SMC can find another Contributor. Note that you may not have the opportunity to write a Digest report at a later time. + +## Step 3: Drafting the Report {#step3} + +The purpose of _Digest_ reports is to provide a relatively brief and ideologically-neutral overview of their subject. + +{% hint style="success" %} +#### Your Responsibilities + +1. Read the original source provided in the assignment email +2. Draft an impartial summary of the assignment email +3. Include in the summary **two** links to outside sources +{% endhint %} + +{% tabs %} +{% tab title="Instructions" %} +As a Contributor, you are responsible for the technical and substantive accuracy of the report. Refer to the [Citation, Style, and Substance Guide](reportstylecitation/) for: + +1. What to look for in a case or legislation +2. How to format citations +3. Style guidelines + +**Please be very careful** not to overstate or misrepresent the source. Digest Reports are often on the first page of Google inquiries for cutting-edge cases -- getting it wrong has consequences. If you are unsure how to summarize a particular point, please ask for help. If all else fails, consider paraphrasing or quoting the source. + +Visit [_Digest_](https://jolt.law.harvard.edu/digest/category/?cat=reports) for examples of edited reports. [Here](http://jolt.law.harvard.edu/digest/federal-circuit-flash-digest-basf-corp-v-johnson-matthey-inc) are [several](http://jolt.law.harvard.edu/digest/teva-v-eli-lilly-teva-argues-lilly-is-infringing-migraine-drug-patent-in-the-united-states) [examples](http://jolt.law.harvard.edu/digest/ubers-august-settlement-with-the-ftc-and-new-data-insecurity-revelations). + +**Length** - while the report’s length will vary with the complexity of the subject, generally the report should be no longer than 500–700 words. The purpose of the report is to provide an accurate overview of the most important aspects of the subject. Readers interested in further detail can visit the primary and secondary sources that will be included. + +**Google Docs** - Please use Google Docs to draft, share, and edit your piece. + +### Report Structure & Organization + +Please ensure that each submission adheres to the general organizational format described below. Contributors should not include their own independent analysis of the subject. **Any analysis** in the report should be clearly attributed to the source: either the _court_ \(by so stating\) or to an _author_ \(by linking to the source\). The standard structure is as follows. + +1. **Report Title** beginning with the colloquial case name; +2. **By-line**, including names of the Contributor and the Editor; +3. **Citation** to the subject, in the standard Digest format, and a hyperlink to the primary source; +4. **Opening Synopsis** + * Brief description of the subject \(one or two sentences\) + * Short summary of the principal holdings, important legislative provisions, or reasons why the event being described is important \(one or two paragraphs\) +5. **Other Analysis** + * Description of the subject \(see the resources following this structure for more subject-specific information\) + * Significance of subject according to the source \(case--court; legislation--legislature\) + * Significance of subject according to secondary sources \(e.g. expert blogs\) +6. **Additional Resources** + 1. Commentary: news articles, if accurate, & scholarly comment + 2. Related materials +7. Optional: one line describing yourself and your interests which will be included at the end of your contributor post. e.g. "\[Contributor’s name\] is a \(1L, 2L, 3L\) at the Harvard Law School." +{% endtab %} + +{% tab title="Sample Case Report" %} +Examples can be found [here](http://jolt.law.harvard.edu/digest/doj-v-bmi-doj-argues-bmis-fractional-licensing-practice-violates-consent-decree) and [here](http://jolt.law.harvard.edu/digest/supreme-court-issues-landmark-ruling-on-fashion-and-design-copyright). + +> **Tags:** \[Work with your Report Editor to come up with tags. Guidelines are available [here](reporteditorguide.md#tags)\] +> **Social Media Line:** U.S. surveillance programs collect \#Verizon metadata and access participating company servers goo.gl/wGBFQ \#privacy +> +> **\[Title\]** +> By \[author\] – Edited by \[editor\] +> \[Full citation of main case, hyperlinked to a primary source. See [Citations](reportstylecitation/#citations) for an example.\] +> +> The \[insert court name\] \(affirmed/reversed/reversed & vacated\) the \[insert lower court name\], which had \[insert description of lower court’s holding & order\]. +> +> The \[insert court name\] held that \[insert 2–3 sentence description of holding & any relevant reasoning\]. In so holding, the court \(stated/noted that\) \[insert description of any interesting/significant legal analysis, particularly of any underlying statutes or policy\]. +> +> \[insert brief discussion of the relevant facts\]. In holding as it did, the court reasoned that \[insert reasoning\]. +> +> \[insert judge name\] dissented. The dissent would have held \[insert description of dissent’s preferred resolution & reasoning underlying dissent\]. +> +> The \[insert hyperlink\] provides an overview of the case. \[insert hyperlink to commentary\] criticizes the decision \[insert one-phrase summary of criticism\]. \[Insert brief 2–4 sentence discussion of why case is significant \(if known\)\] +{% endtab %} + +{% tab title="" %} + +{% endtab %} + +{% tab title="Sample Legislation Report" %} +See [example](https://jolt.law.harvard.edu/digest/coalition-of-32-state-ags-outline-opposition-to-federal-preemption-of-state-data-breach-notification-laws). + +> **Tags:** \[Work with your Report Editor to come up with tags. Guidelines are available [here](reporteditorguide.md#tags)\] +> **Social Media Line:** U.S. surveillance programs collect \#Verizon metadata and access participating company servers goo.gl/wGBFQ \#privacy +> +> **\[Title\]** +> By \[author\] – Edited by \[editor\] +> +> \[House or Senate number\] – \[Name of the Act\] +> \[link to the full text of the bill\] +> \[link to the Senate Vote Summary\] +> \[link to the GovTrack.us Summary\] +> +> On \[insert date\], the House/Senate passed \[insert name of legislation\]. This legislation \[insert brief description of major provisions of bill and what it is designed to do.\] The bill was originally introduced by \[insert congressman name\] \(R/D-\[party affiliation\]\). Prior to its passage, it was amended \[briefly describe nature of amendments\]. According to \[state source — committee report, floor debate, news release\], the purpose of the legislation is to \[insert brief description of purpose\]. +> +> A summary of the history surrounding the bill is available here \[insert hyperlink\] +> \[insert hyperlink to commentary\] calls the legislation a \[insert quote or commentary\]. +> +> \[insert brief discussion of significance\] +{% endtab %} +{% endtabs %} + +## Step 4: Forwarding the Report {#step4} + +{% hint style="success" %} +#### Your Responsibilities + +1. Comment sections of your Report that you believe need a closer review +2. Share your draft on Google Doc +3. Work with the Editor to finalize the piece +4. Be available for any follow-up edits from the Subject Matter Coordinator +{% endhint %} + +Please share your draft on Google Doc with the following: + +* Report Editor +* Assigning Subject Matter Coordinator +* Digest Executive Editor \(joltdigest@mail.law.harvard.edu\) + +The easiest way to do this is to share a link in the assigning email thread. The Editor will have about three days to add comments and suggestions in the Google Doc. Please review them, finalize the draft, and notify the assigning SMC \(via the email thread\). The SMC will take one last look and may offer an additional round of comments to be reviewed before sending it to production. + +Expect a follow-up email from the SMC once your piece goes live. + +## Thank you! + +The _JOLT Digest_ team thanks you for the time you will be putting into creating Digest content. We hope you enjoy the content creation process and working with the subject matter of your assignments. Please feel free to email the [_Digest Masthead_](https://jolt.law.harvard.edu/masthead) if you have any concerns or suggestions on improving the process! + diff --git a/reports/reporteditorguide.md b/reports/reporteditorguide.md new file mode 100644 index 0000000..9b995f3 --- /dev/null +++ b/reports/reporteditorguide.md @@ -0,0 +1,41 @@ +# Editor's Guide + +## Welcome to the Report Editor's Guide! + +This guide will provide an overview of your responsibilities as a **Editor** of a _**Digest**_ **Report**. Reports are short, objective overviews, 500-700 words in length, of recent court opinions or pieces of legislation. They also provide links to primary sources and additional commentary for readers who want to dig deeper. + +Subject Matter Coordinators \(SMCs\) are constantly looking for “hot” law & technology news. They will assign the topic to you and an Report Editor. Your job as the Report Editor is to ensure it is publication-ready. + +{% hint style="info" %} +## Editing Process in a Nutshell + +* [Step 1](reporteditorguide.md#step1): Getting Started +* [Step 2](reporteditorguide.md#step2): Receiving AND Confirming Receipt of Your Assignment +* [Step 3](reporteditorguide.md#step4): Editing +* [Step 4](reporteditorguide.md#step5): Moving the Report Forward +{% endhint %} + +## Step 1: Getting Started {#step1} + +You, the _Digest_ Report Editor, is tasked with reviewing the Contributor's draft for substantive and technical accuracy. You will usually have about three days after the Contributor has shared the first draft to give comments and suggestions. You'll be working with the Contributor in finalizing the draft before the Contributor hands it off to the SMC and Digest Submissions Editor \(Wendy Chu\) for a final review and publication. + +In the event you are unable to complete an assignment, please notify the assigning Coordinator immediately. If your availability changes during the year, notify the [Digest Executive Editor](https://jolt.law.harvard.edu/masthead). + +## Step 2: Receiving and Confirming Receipt of Your Assignment {#step2} + +Please see [Step 2 in the Contributor's Guide](reportcontributorguide.md#step-2-receiving-and-confirming-receipt-of-your-assignment). + +## Step 3: Editing {#step4} + +As an Report Editor, you will work with the Contributor to ensure the report is publication-ready. You should make sure that the Contributor's piece follows the [Style & Citations Guide](reportstylecitation/) and comply with the recommendations laid out in [Step 3 of the Contributor's Guide](reportcontributorguide.md#step3). + +Enter your edits directly into the Google Docs in ["Suggest Edits" mode](https://support.google.com/docs/answer/6033474?co=GENIE.Platform%3DDesktop&hl=en). + +## Step 4: Moving the Report Forward {#step5} + +The Contributor will have shared in the assigning email thread the link to the Google Doc containing the draft \(see [Step 4 of the Contributor's Guide](reportcontributorguide.md#step4) for more details\). Make your comments and suggestions directly within the Google Doc. Once you're done with your comments and suggestions, reply all in the assigning email threads letting everyone know \(1\) a summary of your edits; and \(2\) any questions/concerns that arose during editing. + +## Thank you! + +The JOLT Digest team thanks you for your time and energy. Please feel free to email the [_Digest Masthead_](https://jolt.law.harvard.edu/masthead) if you have any concerns or suggestions on improving the process! + diff --git a/reports/reportstylecitation/README.md b/reports/reportstylecitation/README.md new file mode 100644 index 0000000..6fff4bf --- /dev/null +++ b/reports/reportstylecitation/README.md @@ -0,0 +1,243 @@ +# Style & Citations Guide + +This guide will provide an overview of how to review the **substantive** and **technical** accuracy of a Digest Report. Digest Reports, as compared to Digest Commentaries, are brief summaries of important developments in law and technology. The purpose of Digests Reports is to break down complex legal and technical issues for readers who may not be familiar with the topic. The Digest Reports page also serves as a resource for attorneys who practice within the field of Internet and technology law to keep them apprised of new precedent or legislation. + +## Requirements {#requirements} + +**All** articles should hyperlink to the original source material, preferably a PDF \(e.g., court opinion or filing, legislation\). Additionally, we recommend that all articles should have at least 2 hyperlinks to related material and/or commentary. They can include: + +* Briefs \(filed by the party or amicus\) +* Legal blogs +* News articles + +Contributions should pull from a variety of sources and should be more than just reiterations of existing commentary or reporting. The 2-link minimum is exactly that – a minimum. Points should generally be well supported and should link to related content whenever possible. + +## Style {#style} + +Since Digest is available online, some formatting preferences may be different, so this Digest citation guide supersedes the generic JOLT Style Guide. Below are some common items to check: + +* Only one space between sentences. +* Do not include spaces around an em dash \(“—“\) +* Quotation marks around acronyms located in parentheticals, e.g. Digital Millennium Copyright Act of 1998 \(“DMCA”\) +* Do not capitalize mid-sentence generic party names: plaintiff, defendant, appellee, and appellant +* Do not hyphenate the following words: decisionmaker, factfinder +* Do not use underlining for emphasis. This can easily be mistaken for a broken link. + +## Commas {#commas} + +When listing three or more things, separate each pair with a comma, including the last pair. The last comma precedes the coordinating conjunction \(e.g. _and_ or _or_\). + +> **Example:** Lions, tigers, and bears. + +## Symbols {#symbols} + +Outside of citations, do not use "§" and "¶." Instead, always spell out and capitalize "Section" and "Paragraphs" in place of symbols. + +## Quotations {#quotations} + +If you are quoting a source, make sure to review the Bluebook Rule 5: Quotations for formatting, alterations, internal quotations, and omissions. + +**Block Quotes** — avoid them. You’ll already be linking the reader to the source so there’s no need to quote in length. The exception to this rule, though, is the situation when you are analyzing statutory language; in that case, having the statute conveniently displayed in the body of the article is encouraged. + +## Citations {#citations} + +Despite the Digest’s more informal style, we strive to maintain the high standards for JOLT student writing by citing sources consistently. + +Documents that are the focus of an article, such as a slip opinion, statute, letter, etc., should be properly Bluebooked and located at the beginning of the article. Pincites should not be included throughout the article. + +> **DOJ v. BMI: DOJ Argues BMI’s Fractional Licensing Practice Violates Consent Decree** +> By \[author\] -- Edited by \[editor\] +> Brief of Appellant, United States v. Broadcast Music, Inc., No. 16-3830-cv \(2d. Cir. May 18, 2017\), [brief](http://www.djcounsel.com/wp-content/uploads/2017/05/2017-DOJ-Brief-BMI-Full-Work-Licensing.pdf) hosted by DJ Counsel. +> +> ... body ... + +### Online News Sources + +Support your statements that derive from online news sources by creating hyperlinks out of parts of the statement. Select which words should be hyperlinked in the following preference. + +1. Name of the blog, newspaper, website +2. Name of the author +3. Operative phrase when the statement does not contain either \(1\) or \(2\) + +> **Example:** [Ars Technica](https://arstechnica.com/tech-policy/2009/04/google-loses-on-appeal-will-face-adwords-trademark-suit/) provides commentary. +> **Not:** Ars Technica [provides](https://arstechnica.com/tech-policy/2009/04/google-loses-on-appeal-will-face-adwords-trademark-suit/) commentary. + +Generally, a blog’s name is preferred over the author; however, the author’s name may be included as desired. If it is a personal blog bearing the name of the sole contributor to the blog, the name of the author may be used. + +> **Example:** [Eric Posner](http://ericposner.com/what-has-been-the-effect-of-the-convention-against-torture/) provides commentary. +> **Example:** Stewart Baker on [The Volokh Conspiracy](http://www.volokh.com/2014/01/01/obama-administration-dominates-2014-awards-dubious-achievements-privacy-law/) reviews the Privies. + +Where it is awkward or undesirable to name the source in the sentence, create a hyperlink out of the group of words that the source best supports. Finding the right group of words can be a bit of an art, so work with your Editor on this. + +> **Example:** In May 2009, [the European Commission fined Intel](http://ec.europa.eu/competition/sectors/ICT/intel.html) a record 1.06 billion Euros for abusing its dominant market position. +> **Example:** While prosecution [placed significant emphasis](https://www.nytimes.com/2017/06/06/us/suicide-texting-manslaughter-trial.html) on the text messages between the Carter and Roy during the trial, focusing particularly on the fact that their relationship was so tied to online communication, the judge rested his conclusion on a phone call they exchanged shortly before Roy’s suicide. +> **Not:** While prosecution placed significant [emphasis](https://www.nytimes.com/2017/06/06/us/suicide-texting-manslaughter-trial.html) on the text messages between the Carter and Roy during the trial, focusing particularly on the fact that their relationship was so tied to online communication, the judge rested his conclusion on a phone call they exchanged shortly before Roy’s suicide. + +### Law Review Articles + +In-text citations to law review articles need not be in Bluebook format, but should indicate the name of the author\(s\) and link to a PDF of the article. As with online news sources, hyperlink the name of the source where possible, but put the link on a descriptive phrase otherwise. + +> **Example:** The Innovator’s Patent Agreement bears similarities to the [defensive patent license \(“DPL”\) proposed](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2040945) by Jason Schultz and Jennifer Urban. + +### Statutes + +If a statute is available through an open access online source, such as through the Cornell Legal Information Institute, hyperlink to the source in text, and then Bluebook the source when it is cited. When referring to an act generally, cite to the first U.S.C. section of the Act. When referring to a particular provision of an act for the first time, include a hyperlink to that provision. The hyperlinked text should be the location in the United States Code. + +Make sure to spell out the official name of the act the first time it is cited. + +> **Example:** [Visual Artists Rights Act of 1990](http://www.law.cornell.edu/uscode/17/usc_sec_17_00000106---A000-.html) \(“VARA”\), 17 U.S.C. § 106A \(2012\), a U.S. law offering moral rights to visual artists, is similarly limited. +> **Example:** Section 2520 of the Wiretap Act of 1968 \(“Wiretap Act”\), [18 U.S.C. § 2520](https://www.law.cornell.edu/uscode/text/18/2520), provides a private right of action against persons who violate the provisions of Section 2511 of the Wiretap Act, [18 U.S.C. § 2511](https://www.law.cornell.edu/uscode/text/18/2511). + +### Cases & Court Documents + +Bluebook cases in full the first time they are cited and use an unambiguous shortened case name thereafter. Case names in the full cite should not be italicized if it is hyperlinked. For aesthetic purposes, do not include pincites throughout the article. + +> **Example:** [Fourco Glass Co. v. Transmirra Products Corp.](https://www.law.cornell.edu/supremecourt/text/353/222), 353 U.S. 222 \(1957\) +> **Example:** _Fourco Glass Co. v. Transmirra Products Corp._, 353 U.S. 222 \(1957\) +> **Not:** [_Fourco Glass Co. v. Transmirra Products Corp._](https://www.law.cornell.edu/supremecourt/text/353/222), 353 U.S. 222 \(1957\) + +Shortened case names should always be italicized and never hyperlinked. + +> **Example:** _Fourco Glass_ +> **Not:** Fourco Glass +> **Not:** [_Fourco Glass_](https://www.law.cornell.edu/supremecourt/text/353/222) + +However, procedural phrases like _In re_ should always be italicized, even if they are part of hyperlinks. + +Remember that, for purposes of short forms, a citation to a court document including a case citation suffices as a citation to the case itself \(Rule 10.8.3\). + +Since _Digest_ posts are often more recent than print articles, they often rely on pending cases, rule 10.8.\* Make sure to cite slip opinions \(rule 10.8.1\(b\)\) and cases decided en banc \(rule 10.6.1\) as appropriate. + +**Abbreviations** -- As per Bluebook Rule 10.2.1\(c\), when citing within the text, only abbreviate obvious names \(e.g. NLRB, EPA\) and any of the following eight words, but only if they do not begin a party’s name: “&,” “Ass’n,” “Bros.,” “Co.,” “Corp.,” “Inc.,” “Ltd.,” and “No.” + +Where case names are included in endnotes, follow case name abbreviations in Table 6 of the Bluebook. + +**Hosted By** -- If a PDF of a court document is available through an open access online source \(i.e., not through Westlaw or Lexis Nexis\), hyperlink to the source from the document type or, if none, case name in the Bluebook citation. If the PDF is hosted by a non-court source, include “hosted by” language with the hyperlink on the document type \(not a Bluebook abbreviation\). + +> **Example:** [MGA Entertainment, Inc. v. Mattel, Inc.](http://www.sunsteinlaw.com/media/BratzTCC.pdf), No. 09-55673 \(9th Cir. July 22, 2010\), hosted by sunsteinlaw.com. +> **Example:** Viacom International Inc. v. YouTube, Inc., No. 07 Civ. 2103 \(S.D.N.Y. June 23, 2010\), [slip opinion](http://docfiles.justia.com/cases/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf), hosted by Justia.com. +> **Example:** Complaint for Declaratory Judgment and Injunctive Relief, GoldieBlox, Inc. v. Island Def Jam Music Group, A Div. of UMG Recordings, Inc., No. 3:13-cv-05428 \(N.D. Cal. Nov. 21, 2013\), [complaint](http://www.scribd.com/doc/186402972/Beastie) hosted by Scribd. +> **Not:** Viacom Int’l Inc. v. YouTube, Inc., No. 07 Civ. 2103 \(S.D.N.Y. June 23, 2010\), [slip op.](https://cases.justia.com/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf) hosted by Justia.com + +## Substance {#substance} + +Keep in mind that the value of _Digest_ depends heavily on its accuracy. Please check your piece against the following guidelines **before** emailing the draft. + +**Cases** -- If the topic deals extensively with statutes or previous previous cases, please be sure those are mentioned and briefly described in the article. If possible, please also hyperlink to an online source \(particularly Digest coverage of previous cases, if available\). + +**Holding** -- Make sure the article accurately reports case or administrative holdings. Think about both broad and narrow potential holdings. Consider the following points. + +* Who wrote the decision? Was the decision unanimous? +* What did the lower court do? Why? +* What facts, precedent, or law did the court cite in support of its holding? +* What legal tests or rules did the court apply? + +**Dissent or Concurrence** -- state the reasons for the dissent or concurrence and what points the court or panel diverged. + +**Significance** -- Consider whether the holding + +* creates a circuit split. +* clarifies \(or confuses\) a particular point of law. +* creates a new legal test. Consider also mentioning whether the new test is more or less difficult to meet than the old one. +* is the first to construe a particular statute. +* expands or narrows rights of particular parties. +* is the resolution of a long-running legal dispute. +* concerns a innovation of significant public interest. + +**Legislation** -- be sure to include the following + +* official name of the legislation +* sponsors and supporters +* major provisions \(often identifiable from the headings\) +* history surrounding the bill and major differences \(if any\) between House and Senate bills +* methods and penalties for enforcing compliance +* articulate rationale for the legislation; distinguish between rationales **in** the legislation and those you see in floor debates, press releases, or commentary +* significance, consider + * whether this is the first legislation to regulate this area and/or what other states have enacted similar legislation. + * what, if any, legislation is modified by the proposal. + * the significance of the legislation. + * whether it expands/narrows the rights of particular parties. + * what \(if any\) industries have supported or opposed the bill. + +**Reasoning** -- make sure the article accurately reports any reasoning to the extent possible in a summary. In particular, identify and describe legal tests. + +**Policy purpose** -- for cases or legislation, provide any policy rationales identified in the primary sources. + +**Context** -- make sure the article provides sufficient context to orient a reader only vaguely familiar with the subject. + +**Tone** -- should be neutral and descriptive. Reporting controversy is okay; taking a side in the controversy is not. + +**Links** -- check that all your hyperlinks point to the correct site and that all sources or mentioned cases or legislation are hyperlinked where possible. + +## Locating Relevant Material and Commentary {#relevant} + +**All** articles should hyperlink to the original source material \(e.g., court opinion or filing, legislation\). In addition, all articles should have **at least** 2 hyperlinks to related materials and/or commentary. They can include: + +* Briefs \(filed by the party or amicus\) +* Legal blogs +* News articles + +### Locating Hyperlinks + +Below is a rough procedure for identifying possible hyperlinks: + +1. Quickly check for blog posts +2. Check Westlaw/LexisNexis \(for cases\) or Congressional websites \([http://www.house.gov/](http://www.house.gov/) or [http://www.senate.gov/](http://www.senate.gov/)\) for related materials, including: + * related/competing legislation + * briefs filed or past orders +3. Google search for the case or legislation. Consider linking to any resulting + * **blog links.** To search legal blogs, please use Google Blog Search + * **SSRN papers** \(include "SSRN" as a keyword in the Google search\) +4. Search for JOLT articles: In **Westlaw** use the database "HVJLT" and use keywords from the case. Suggest any results that discuss the related topic. +5. Search for JOLT _Digest_ articles on the _Digest_ website. Use the search bar to search for related articles. + +### Key Blogs + +* How Appealing [http://howappealing.law.com](http://howappealing.law.com) +* Patently-O [http://patentlyo.com](http://patentlyo.com) +* Slashdot / Your Rights Online [http://yro.slashdot.org](http://yro.slashdot.org) +* ArsTechnica [http://arstechnica.com/search.ars?Tag=law](http://arstechnica.com/search.ars?Tag=law) +* SCOTUS Blog: [http://www.scotusblog.com/wp/](http://www.scotusblog.com/wp/) +* Citizen Media Law Project Blog [http://www.citmedialaw.org/blog](http://www.citmedialaw.org/blog) +* Trademark Blog [http://www.schwimmerlegal.com/](http://www.schwimmerlegal.com/) +* Info/Law [http://blogs.law.harvard.edu/infolaw/](http://blogs.law.harvard.edu/infolaw/) +* Patent Appeal Tracer [http://www.patracer.com/FBI](http://www.patracer.com/FBI) +* FOIA Vault [https://vault.fbi.gov/recently-added](https://vault.fbi.gov/recently-added) +* Likelihood of Confusion [http://www.likelihoodofconfusion.com/](http://www.likelihoodofconfusion.com/) +* Technology & Marketing Law Blog \(Eric Goldman\) [http://blog.ericgoldman.org/](http://blog.ericgoldman.org/) +* Internet Cases [http://blog.internetcases.com/](http://blog.internetcases.com/) +* Copyrights & Campaigns [http://copyrightsandcampaigns.blogspot.com/](http://copyrightsandcampaigns.blogspot.com/) +* EFF Deeplinks blog [http://www.eff.org/deeplinks](http://www.eff.org/deeplinks) +* Wired Threat Level [http://blog.wired.com/27bstroke6/](http://blog.wired.com/27bstroke6/) +* Patent Prospector [http://www.patenthawk.com/blog/](http://www.patenthawk.com/blog/) +* Wall Street Journal Law Blog [http://blogs.wsj.com/law/](http://blogs.wsj.com/law/) +* Stanford Cyberlaw blogs [http://cyberlaw.stanford.edu/people-and-blogs](http://cyberlaw.stanford.edu/people-and-blogs) + +### Recent Appellate Opinions + +* Supreme Court: [http://www.supremecourtus.gov/opinions/08slipopinion.html](http://www.supremecourtus.gov/opinions/08slipopinion.html) +* Federal Circuit: [http://www.cafc.uscourts.gov/opinions-orders/search/report.html](http://www.cafc.uscourts.gov/opinions-orders/search/report.html) +* D.C. Circuit: [http://www.cadc.uscourts.gov/bin/opinions/allopinions.asp](http://www.cadc.uscourts.gov/bin/opinions/allopinions.asp) +* 1st Circuit: [http://www.ca1.uscourts.gov/opinions/opinion.php?InOpn=1](http://www.ca1.uscourts.gov/opinions/opinion.php?InOpn=1) +* 2nd Circuit: [http://www.ca2.uscourts.gov/opinions.htm](http://www.ca2.uscourts.gov/opinions.htm) +* 3rd Circuit: [http://www.ca1.uscourts.gov/opinions/opinion.php?InOpn=](http://www.ca1.uscourts.gov/opinions/opinion.php?InOpn=) +* 4th Circuit: [http://pacer.ca4.uscourts.gov/opinions\_week.htm](http://pacer.ca4.uscourts.gov/opinions_week.htm) +* 5th Circuit: [http://www.ca5.uscourts.gov/Opinions.aspx?View=Last7](http://www.ca5.uscourts.gov/Opinions.aspx?View=Last7) +* 6th Circuit: [http://www.ca6.uscourts.gov/internet/opinions/opinions.php](http://www.ca6.uscourts.gov/internet/opinions/opinions.php) +* 7th Circuit: [http://www.ca7.uscourts.gov/fdocs/docs.fwx?dname=opinion](http://www.ca7.uscourts.gov/fdocs/docs.fwx?dname=opinion) +* 8th Circuit: [http://www.ca8.uscourts.gov/cgi-bin/new/today2.pl](http://www.ca8.uscourts.gov/cgi-bin/new/today2.pl) +* 9th Circuit: [http://www.ca9.uscourts.gov/ca9/newopinions.nsf/](http://www.ca9.uscourts.gov/ca9/newopinions.nsf/) +* 10th Circuit: [http://www.ca10.uscourts.gov/clerk/casemanagement.php](http://www.ca10.uscourts.gov/clerk/casemanagement.php) +* 11th Circuit: [http://www.ca11.uscourts.gov/](http://www.ca11.uscourts.gov/) + +### Court Filings + +* Lexis/Westlaw \(briefs or motions for decided cases\) +* [Justia](http://dockets.justia.com/) \(free access to many federal district court civil filings for ongoing cases\) +* [PACER](http://pacer.psc.uscourts.gov/) \(JOLT can reimburse you for fees incurred in downloading\) + +### Legislative Sources + +* THOMAS Daily Digest [http://thomas.loc.gov/cgi-bin/dailydigest](http://thomas.loc.gov/cgi-bin/dailydigest) +* Bills Signed by the President [http://www.whitheouse.gov/news/](http://www.whitheouse.gov/news/) + diff --git a/reports/reportstylecitation/citations.md b/reports/reportstylecitation/citations.md new file mode 100644 index 0000000..a8c4def --- /dev/null +++ b/reports/reportstylecitation/citations.md @@ -0,0 +1,2 @@ +# Citations + diff --git a/reports/reportstylecitation/commas.md b/reports/reportstylecitation/commas.md new file mode 100644 index 0000000..97a8b97 --- /dev/null +++ b/reports/reportstylecitation/commas.md @@ -0,0 +1,2 @@ +# Commas + diff --git a/reports/reportstylecitation/quotations.md b/reports/reportstylecitation/quotations.md new file mode 100644 index 0000000..ef84a78 --- /dev/null +++ b/reports/reportstylecitation/quotations.md @@ -0,0 +1,2 @@ +# Quotations + diff --git a/reports/reportstylecitation/requirements.md b/reports/reportstylecitation/requirements.md new file mode 100644 index 0000000..c4a55bf --- /dev/null +++ b/reports/reportstylecitation/requirements.md @@ -0,0 +1,2 @@ +# Requirements + diff --git a/reports/reportstylecitation/style.md b/reports/reportstylecitation/style.md new file mode 100644 index 0000000..dec0061 --- /dev/null +++ b/reports/reportstylecitation/style.md @@ -0,0 +1,2 @@ +# Style + diff --git a/reports/reportstylecitation/substance.md b/reports/reportstylecitation/substance.md new file mode 100644 index 0000000..f5a4c25 --- /dev/null +++ b/reports/reportstylecitation/substance.md @@ -0,0 +1,2 @@ +# Substance + diff --git a/reports/reportstylecitation/symbols.md b/reports/reportstylecitation/symbols.md new file mode 100644 index 0000000..9a0ef51 --- /dev/null +++ b/reports/reportstylecitation/symbols.md @@ -0,0 +1,2 @@ +# Symbols + From 6dc517f7b17960fc40d9d5d844b7cbd192bb2152 Mon Sep 17 00:00:00 2001 From: Peter Zhu Date: Thu, 27 Sep 2018 19:58:20 +0000 Subject: [PATCH 02/11] GitBook: [2.0.0] 26 pages modified --- README.md | 2 +- SUMMARY.md | 9 +------ comments/commentstylecitation/citations.md | 2 ++ comments/commentstylecitation/commas.md | 2 ++ comments/commentstylecitation/quotations.md | 2 ++ comments/commentstylecitation/requirements.md | 2 ++ comments/commentstylecitation/style.md | 2 ++ comments/commentstylecitation/symbols.md | 2 ++ notes/notestylecitation/README.md | 2 +- notes/notestylecitation/citations.md | 2 ++ notes/notestylecitation/commas.md | 2 ++ notes/notestylecitation/organization.md | 2 ++ notes/notestylecitation/requirements.md | 2 ++ notes/notestylecitation/style.md | 2 ++ notes/notestylecitation/symbols.md | 2 ++ reports/reportcontributorguide.md | 8 +++---- reports/reporteditorguide.md | 2 +- .../README.md => reportstylecitation.md} | 24 +++++++++++-------- reports/reportstylecitation/citations.md | 2 -- reports/reportstylecitation/commas.md | 2 -- reports/reportstylecitation/quotations.md | 2 -- reports/reportstylecitation/requirements.md | 2 -- reports/reportstylecitation/style.md | 2 -- reports/reportstylecitation/substance.md | 2 -- reports/reportstylecitation/symbols.md | 2 -- 25 files changed, 46 insertions(+), 39 deletions(-) rename reports/{reportstylecitation/README.md => reportstylecitation.md} (88%) delete mode 100644 reports/reportstylecitation/citations.md delete mode 100644 reports/reportstylecitation/commas.md delete mode 100644 reports/reportstylecitation/quotations.md delete mode 100644 reports/reportstylecitation/requirements.md delete mode 100644 reports/reportstylecitation/style.md delete mode 100644 reports/reportstylecitation/substance.md delete mode 100644 reports/reportstylecitation/symbols.md diff --git a/README.md b/README.md index ff8dfe4..3a4a09e 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ The Digest features short articles on new, precedential, or interesting cases; n ## Do you conform with the Oxford Comma? -Yes. Read more [here](reports/reportstylecitation/#commas). +Yes. Read more [here](reports/reportstylecitation.md#commas). ## Meet the editing team! diff --git a/SUMMARY.md b/SUMMARY.md index b4f4722..5acd964 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -6,14 +6,7 @@ * [Contributor's Guide](reports/reportcontributorguide.md) * [Editor's Guide](reports/reporteditorguide.md) -* [Style & Citations Guide](reports/reportstylecitation/README.md) - * [Requirements](reports/reportstylecitation/requirements.md) - * [Style](reports/reportstylecitation/style.md) - * [Commas](reports/reportstylecitation/commas.md) - * [Symbols](reports/reportstylecitation/symbols.md) - * [Quotations](reports/reportstylecitation/quotations.md) - * [Citations](reports/reportstylecitation/citations.md) - * [Substance](reports/reportstylecitation/substance.md) +* [Style & Citations Guide](reports/reportstylecitation.md) ## Notes diff --git a/comments/commentstylecitation/citations.md b/comments/commentstylecitation/citations.md index a8c4def..9208556 100644 --- a/comments/commentstylecitation/citations.md +++ b/comments/commentstylecitation/citations.md @@ -1,2 +1,4 @@ # Citations + + diff --git a/comments/commentstylecitation/commas.md b/comments/commentstylecitation/commas.md index 97a8b97..dbcd876 100644 --- a/comments/commentstylecitation/commas.md +++ b/comments/commentstylecitation/commas.md @@ -1,2 +1,4 @@ # Commas + + diff --git a/comments/commentstylecitation/quotations.md b/comments/commentstylecitation/quotations.md index ef84a78..45f9d94 100644 --- a/comments/commentstylecitation/quotations.md +++ b/comments/commentstylecitation/quotations.md @@ -1,2 +1,4 @@ # Quotations + + diff --git a/comments/commentstylecitation/requirements.md b/comments/commentstylecitation/requirements.md index c4a55bf..064ad23 100644 --- a/comments/commentstylecitation/requirements.md +++ b/comments/commentstylecitation/requirements.md @@ -1,2 +1,4 @@ # Requirements + + diff --git a/comments/commentstylecitation/style.md b/comments/commentstylecitation/style.md index dec0061..738b291 100644 --- a/comments/commentstylecitation/style.md +++ b/comments/commentstylecitation/style.md @@ -1,2 +1,4 @@ # Style + + diff --git a/comments/commentstylecitation/symbols.md b/comments/commentstylecitation/symbols.md index 9a0ef51..4b1db98 100644 --- a/comments/commentstylecitation/symbols.md +++ b/comments/commentstylecitation/symbols.md @@ -1,2 +1,4 @@ # Symbols + + diff --git a/notes/notestylecitation/README.md b/notes/notestylecitation/README.md index add6f34..5107c8d 100644 --- a/notes/notestylecitation/README.md +++ b/notes/notestylecitation/README.md @@ -37,7 +37,7 @@ There are also some additional requirements specific to a _Digest_ Note: ## Commas {#commas} -Use the serial comma. Read [here](../../reports/reportstylecitation/#commas) for more information. +Use the serial comma. Read [here](../../reports/reportstylecitation.md#commas) for more information. ## Symbols {#symbols} diff --git a/notes/notestylecitation/citations.md b/notes/notestylecitation/citations.md index a8c4def..9208556 100644 --- a/notes/notestylecitation/citations.md +++ b/notes/notestylecitation/citations.md @@ -1,2 +1,4 @@ # Citations + + diff --git a/notes/notestylecitation/commas.md b/notes/notestylecitation/commas.md index 97a8b97..dbcd876 100644 --- a/notes/notestylecitation/commas.md +++ b/notes/notestylecitation/commas.md @@ -1,2 +1,4 @@ # Commas + + diff --git a/notes/notestylecitation/organization.md b/notes/notestylecitation/organization.md index c3aae8d..b7d67ea 100644 --- a/notes/notestylecitation/organization.md +++ b/notes/notestylecitation/organization.md @@ -1,2 +1,4 @@ # Organization + + diff --git a/notes/notestylecitation/requirements.md b/notes/notestylecitation/requirements.md index c4a55bf..064ad23 100644 --- a/notes/notestylecitation/requirements.md +++ b/notes/notestylecitation/requirements.md @@ -1,2 +1,4 @@ # Requirements + + diff --git a/notes/notestylecitation/style.md b/notes/notestylecitation/style.md index dec0061..738b291 100644 --- a/notes/notestylecitation/style.md +++ b/notes/notestylecitation/style.md @@ -1,2 +1,4 @@ # Style + + diff --git a/notes/notestylecitation/symbols.md b/notes/notestylecitation/symbols.md index 9a0ef51..4b1db98 100644 --- a/notes/notestylecitation/symbols.md +++ b/notes/notestylecitation/symbols.md @@ -1,2 +1,4 @@ # Symbols + + diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md index 4a901dd..b07ba5f 100644 --- a/reports/reportcontributorguide.md +++ b/reports/reportcontributorguide.md @@ -35,7 +35,7 @@ The SMC will send you and the Report Editor an assigning email with: 1. Background \(parties, procedural posture, etc.\) 2. Significance of the case/legislation 3. Link or attachment to primary source -4. Link to [Contributor](reportcontributorguide.md#welcome-to-the-report-contributors-guide), [Editor](reporteditorguide.md#welcome-to-the-report-editors-guide), and [Style & Citation Guide](reportstylecitation/) +4. Link to [Contributor](reportcontributorguide.md#welcome-to-the-report-contributors-guide), [Editor](reporteditorguide.md#welcome-to-the-report-editors-guide), and [Style & Citation Guide](reportstylecitation.md) 5. Credentials for online Bluebook access If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Executive Editor, who are also available to answer questions. @@ -74,7 +74,7 @@ In addition to summarizing the case, your article should also include at least 2 You can find an example of a Digests post [here](http://jolt.law.harvard.edu/digest/two-way-media-v-comcast). -You should follow the appropriate Digest Report guides: [Style & Citations Guide](reportstylecitation/), [Contributor's Guide](reportcontributorguide.md), and [Editor's Guide](reporteditorguide.md). On occasion, the Style Guide requires you to follow the Bluebook \(though we never pincite\). JOLT maintains several online bluebook accounts to help with that process. Log-in with the following credentials at [www.legalbluebook.com](http://www.legalbluebook.com/). +You should follow the appropriate Digest Report guides: [Style & Citations Guide](reportstylecitation.md), [Contributor's Guide](reportcontributorguide.md), and [Editor's Guide](reporteditorguide.md). On occasion, the Style Guide requires you to follow the Bluebook \(though we never pincite\). JOLT maintains several online bluebook accounts to help with that process. Log-in with the following credentials at [www.legalbluebook.com](http://www.legalbluebook.com/). Accounts: \[excluded\] @@ -111,7 +111,7 @@ The purpose of _Digest_ reports is to provide a relatively brief and ideological {% tabs %} {% tab title="Instructions" %} -As a Contributor, you are responsible for the technical and substantive accuracy of the report. Refer to the [Citation, Style, and Substance Guide](reportstylecitation/) for: +As a Contributor, you are responsible for the technical and substantive accuracy of the report. Refer to the [Citation, Style, and Substance Guide](reportstylecitation.md) for: 1. What to look for in a case or legislation 2. How to format citations @@ -153,7 +153,7 @@ Examples can be found [here](http://jolt.law.harvard.edu/digest/doj-v-bmi-doj-ar > > **\[Title\]** > By \[author\] – Edited by \[editor\] -> \[Full citation of main case, hyperlinked to a primary source. See [Citations](reportstylecitation/#citations) for an example.\] +> \[Full citation of main case, hyperlinked to a primary source. See [Citations](reportstylecitation.md#citations) for an example.\] > > The \[insert court name\] \(affirmed/reversed/reversed & vacated\) the \[insert lower court name\], which had \[insert description of lower court’s holding & order\]. > diff --git a/reports/reporteditorguide.md b/reports/reporteditorguide.md index 9b995f3..5e0c938 100644 --- a/reports/reporteditorguide.md +++ b/reports/reporteditorguide.md @@ -27,7 +27,7 @@ Please see [Step 2 in the Contributor's Guide](reportcontributorguide.md#step-2- ## Step 3: Editing {#step4} -As an Report Editor, you will work with the Contributor to ensure the report is publication-ready. You should make sure that the Contributor's piece follows the [Style & Citations Guide](reportstylecitation/) and comply with the recommendations laid out in [Step 3 of the Contributor's Guide](reportcontributorguide.md#step3). +As an Report Editor, you will work with the Contributor to ensure the report is publication-ready. You should make sure that the Contributor's piece follows the [Style & Citations Guide](reportstylecitation.md) and comply with the recommendations laid out in [Step 3 of the Contributor's Guide](reportcontributorguide.md#step3). Enter your edits directly into the Google Docs in ["Suggest Edits" mode](https://support.google.com/docs/answer/6033474?co=GENIE.Platform%3DDesktop&hl=en). diff --git a/reports/reportstylecitation/README.md b/reports/reportstylecitation.md similarity index 88% rename from reports/reportstylecitation/README.md rename to reports/reportstylecitation.md index 6fff4bf..2d91981 100644 --- a/reports/reportstylecitation/README.md +++ b/reports/reportstylecitation.md @@ -1,6 +1,6 @@ # Style & Citations Guide -This guide will provide an overview of how to review the **substantive** and **technical** accuracy of a Digest Report. Digest Reports, as compared to Digest Commentaries, are brief summaries of important developments in law and technology. The purpose of Digests Reports is to break down complex legal and technical issues for readers who may not be familiar with the topic. The Digest Reports page also serves as a resource for attorneys who practice within the field of Internet and technology law to keep them apprised of new precedent or legislation. +Digest Reports are brief summaries of important developments in law and technology. The purpose of Digests Reports is to break down complex legal and technical issues for readers who may not be familiar with the topic. The Digest Reports also serve to keep attorneys who practice within the field of Internet and technology law apprised of new precedent or legislation. ## Requirements {#requirements} @@ -18,7 +18,7 @@ Since Digest is available online, some formatting preferences may be different, * Only one space between sentences. * Do not include spaces around an em dash \(“—“\) -* Quotation marks around acronyms located in parentheticals, e.g. Digital Millennium Copyright Act of 1998 \(“DMCA”\) +* Quotation marks around acronyms located in parenthetical, e.g. Digital Millennium Copyright Act of 1998 \(“DMCA”\) * Do not capitalize mid-sentence generic party names: plaintiff, defendant, appellee, and appellant * Do not hyphenate the following words: decisionmaker, factfinder * Do not use underlining for emphasis. This can easily be mistaken for a broken link. @@ -31,7 +31,7 @@ When listing three or more things, separate each pair with a comma, including th ## Symbols {#symbols} -Outside of citations, do not use "§" and "¶." Instead, always spell out and capitalize "Section" and "Paragraphs" in place of symbols. +Outside of citations, do not use "§" and "¶." Instead, spell out and capitalize "Section" and "Paragraphs" in place of symbols. ## Quotations {#quotations} @@ -43,7 +43,7 @@ If you are quoting a source, make sure to review the Bluebook Rule 5: Quotations Despite the Digest’s more informal style, we strive to maintain the high standards for JOLT student writing by citing sources consistently. -Documents that are the focus of an article, such as a slip opinion, statute, letter, etc., should be properly Bluebooked and located at the beginning of the article. Pincites should not be included throughout the article. +Documents that are the focus of an article, such as a slip opinion, statute, letter, etc., should be properly Bluebooked and located at the beginning of the article. Pincites need not be included throughout the article. > **DOJ v. BMI: DOJ Argues BMI’s Fractional Licensing Practice Violates Consent Decree** > By \[author\] -- Edited by \[editor\] @@ -75,7 +75,7 @@ Where it is awkward or undesirable to name the source in the sentence, create a ### Law Review Articles -In-text citations to law review articles need not be in Bluebook format, but should indicate the name of the author\(s\) and link to a PDF of the article. As with online news sources, hyperlink the name of the source where possible, but put the link on a descriptive phrase otherwise. +In-text citations to law review articles need not be in Bluebook format but should indicate the name of the author\(s\) and link to a PDF of the article. As with online news sources, hyperlink the name of the source where possible, but put the link on a descriptive phrase otherwise. > **Example:** The Innovator’s Patent Agreement bears similarities to the [defensive patent license \(“DPL”\) proposed](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2040945) by Jason Schultz and Jennifer Urban. @@ -108,11 +108,15 @@ Remember that, for purposes of short forms, a citation to a court document inclu Since _Digest_ posts are often more recent than print articles, they often rely on pending cases, rule 10.8.\* Make sure to cite slip opinions \(rule 10.8.1\(b\)\) and cases decided en banc \(rule 10.6.1\) as appropriate. -**Abbreviations** -- As per Bluebook Rule 10.2.1\(c\), when citing within the text, only abbreviate obvious names \(e.g. NLRB, EPA\) and any of the following eight words, but only if they do not begin a party’s name: “&,” “Ass’n,” “Bros.,” “Co.,” “Corp.,” “Inc.,” “Ltd.,” and “No.” +### Abbreviations + +As per Bluebook Rule 10.2.1\(c\), when citing within the text, only abbreviate obvious names \(e.g. NLRB, EPA\) and any of the following eight words, but only if they do not begin a party’s name: “&,” “Ass’n,” “Bros.,” “Co.,” “Corp.,” “Inc.,” “Ltd.,” and “No.” Where case names are included in endnotes, follow case name abbreviations in Table 6 of the Bluebook. -**Hosted By** -- If a PDF of a court document is available through an open access online source \(i.e., not through Westlaw or Lexis Nexis\), hyperlink to the source from the document type or, if none, case name in the Bluebook citation. If the PDF is hosted by a non-court source, include “hosted by” language with the hyperlink on the document type \(not a Bluebook abbreviation\). +### **Hosted Sources** + +If a PDF of a court document is available through an open access online source \(i.e., not through Westlaw or Lexis Nexis\), hyperlink to the source from the document type or, if none, case name in the Bluebook citation. If the PDF is hosted by a non-court source, include “hosted by” language with the hyperlink on the document type \(not a Bluebook abbreviation\). > **Example:** [MGA Entertainment, Inc. v. Mattel, Inc.](http://www.sunsteinlaw.com/media/BratzTCC.pdf), No. 09-55673 \(9th Cir. July 22, 2010\), hosted by sunsteinlaw.com. > **Example:** Viacom International Inc. v. YouTube, Inc., No. 07 Civ. 2103 \(S.D.N.Y. June 23, 2010\), [slip opinion](http://docfiles.justia.com/cases/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf), hosted by Justia.com. @@ -121,7 +125,7 @@ Where case names are included in endnotes, follow case name abbreviations in Tab ## Substance {#substance} -Keep in mind that the value of _Digest_ depends heavily on its accuracy. Please check your piece against the following guidelines **before** emailing the draft. +Keep in mind that the value of _Digest_ depends heavily on its accuracy. Please check your piece against the following guidelines **before** submitting the draft. **Cases** -- If the topic deals extensively with statutes or previous previous cases, please be sure those are mentioned and briefly described in the article. If possible, please also hyperlink to an online source \(particularly Digest coverage of previous cases, if available\). @@ -171,7 +175,7 @@ Keep in mind that the value of _Digest_ depends heavily on its accuracy. Please ## Locating Relevant Material and Commentary {#relevant} -**All** articles should hyperlink to the original source material \(e.g., court opinion or filing, legislation\). In addition, all articles should have **at least** 2 hyperlinks to related materials and/or commentary. They can include: +Reports should hyperlink to the original source material \(e.g., court opinion or filing, legislation\). In addition, all reports should have **at least** 2 hyperlinks to related materials and/or commentary. They can include: * Briefs \(filed by the party or amicus\) * Legal blogs @@ -189,7 +193,7 @@ Below is a rough procedure for identifying possible hyperlinks: * **blog links.** To search legal blogs, please use Google Blog Search * **SSRN papers** \(include "SSRN" as a keyword in the Google search\) 4. Search for JOLT articles: In **Westlaw** use the database "HVJLT" and use keywords from the case. Suggest any results that discuss the related topic. -5. Search for JOLT _Digest_ articles on the _Digest_ website. Use the search bar to search for related articles. +5. Search for [JOLT _Digest_ Report](https://jolt.law.harvard.edu/digest/category/?cat=reports). Use the search bar to search for related articles. ### Key Blogs diff --git a/reports/reportstylecitation/citations.md b/reports/reportstylecitation/citations.md deleted file mode 100644 index a8c4def..0000000 --- a/reports/reportstylecitation/citations.md +++ /dev/null @@ -1,2 +0,0 @@ -# Citations - diff --git a/reports/reportstylecitation/commas.md b/reports/reportstylecitation/commas.md deleted file mode 100644 index 97a8b97..0000000 --- a/reports/reportstylecitation/commas.md +++ /dev/null @@ -1,2 +0,0 @@ -# Commas - diff --git a/reports/reportstylecitation/quotations.md b/reports/reportstylecitation/quotations.md deleted file mode 100644 index ef84a78..0000000 --- a/reports/reportstylecitation/quotations.md +++ /dev/null @@ -1,2 +0,0 @@ -# Quotations - diff --git a/reports/reportstylecitation/requirements.md b/reports/reportstylecitation/requirements.md deleted file mode 100644 index c4a55bf..0000000 --- a/reports/reportstylecitation/requirements.md +++ /dev/null @@ -1,2 +0,0 @@ -# Requirements - diff --git a/reports/reportstylecitation/style.md b/reports/reportstylecitation/style.md deleted file mode 100644 index dec0061..0000000 --- a/reports/reportstylecitation/style.md +++ /dev/null @@ -1,2 +0,0 @@ -# Style - diff --git a/reports/reportstylecitation/substance.md b/reports/reportstylecitation/substance.md deleted file mode 100644 index f5a4c25..0000000 --- a/reports/reportstylecitation/substance.md +++ /dev/null @@ -1,2 +0,0 @@ -# Substance - diff --git a/reports/reportstylecitation/symbols.md b/reports/reportstylecitation/symbols.md deleted file mode 100644 index 9a0ef51..0000000 --- a/reports/reportstylecitation/symbols.md +++ /dev/null @@ -1,2 +0,0 @@ -# Symbols - From c770ff63ac49a1418944d4f3bb176cf05a04d7b3 Mon Sep 17 00:00:00 2001 From: Peter Zhu Date: Sun, 20 Jan 2019 15:13:45 +0000 Subject: [PATCH 03/11] GitBook: [2.0.0] 8 pages modified --- comments/commentcontributorguide.md | 10 +++++----- comments/commentstylecitation/README.md | 12 ++++++------ notes/notecontributorguide.md | 12 ++++++------ notes/noteeditorguide.md | 10 +++++----- notes/notestylecitation/README.md | 12 ++++++------ reports/reportcontributorguide.md | 10 +++------- reports/reporteditorguide.md | 8 ++++---- reports/reportstylecitation.md | 16 ++++++++-------- 8 files changed, 43 insertions(+), 47 deletions(-) diff --git a/comments/commentcontributorguide.md b/comments/commentcontributorguide.md index e948bbf..086a931 100644 --- a/comments/commentcontributorguide.md +++ b/comments/commentcontributorguide.md @@ -6,7 +6,7 @@ The JOLT _Digest_ Commentary section is a new platform for professionals, academ _Digest_ Comments are about 2,000 words and can come in several general forms: opinion pieces, primers, or responses. This guide will provide an overview of your responsibilities as the author of a _Digest_ Comment. -## Writing Process in a Nutshell {#nutshell} +## Writing Process in a Nutshell The Commentary writing process can be broken down into the following steps. @@ -15,7 +15,7 @@ The Commentary writing process can be broken down into the following steps. * [Step 3](commentcontributorguide.md#step3): Digest Masthead Edits * [Step 4](commentcontributorguide.md#step4): Finalizing the Comment -## Step 1: Getting Started {#step1} +## Step 1: Getting Started You, the Comment author, are hoping to publish a Comment with JOLT _Digest_. Your first task is to come up with a topic. Because Comments should be timely and related to law and technology, you can run your topic by the Digest Executive Editor. However, you can also submit a draft without asking us beforehand. @@ -43,7 +43,7 @@ A primer can also address several issues related to the topic. For example, you Response pieces must reply to a JOLT publication. We strongly favor responses to articles published in our print edition. Authors should clearly identify the contested article, acknowledge where they agree with the JOLT publication and where they disagree. JOLT _Digest_ will inform the author of the contested article that a response is being drafted so that he or she has the option to draft a rebuttal. -## Step 2: Drafting the Comment {#step2} +## Step 2: Drafting the Comment If seeking our approval for your topic, you must send us a draft within two \(2\) weeks of receiving our confirmation. The Comment must be consistent with the [Digest Commentary Style Guide](commentstylecitation/). @@ -51,11 +51,11 @@ The final Comment should be around 2,000 words in length. Because Digest’s rea You may include a short biography at the end of the Comment, as well as links to your social media accounts. -## Step 3: Digest Masthead Edits {#step3} +## Step 3: Digest Masthead Edits Please send your completed draft to the Digest Executive Editor \(currently Filippo Raso\). The Digest Executive Editor will review the Comment for factual accuracy, compliance with the style guide, and organization. The Digest Executive Editor will only reject claims that are patently untrue, though he may request additional sources to establish the validity of a claim. -## Step 4: Finalizing the Comment {#step4} +## Step 4: Finalizing the Comment The Digest Executive Editor will return the Comment to you for your final review. Please address his comments. With your approval, he will post the final article on the Digest Commentary page. diff --git a/comments/commentstylecitation/README.md b/comments/commentstylecitation/README.md index 0360621..a8948ed 100644 --- a/comments/commentstylecitation/README.md +++ b/comments/commentstylecitation/README.md @@ -4,11 +4,11 @@ Authors should review the Style and Citation Guide before they begin drafting their Comment. -## Requirements {#requirements} +## Requirements All Comments should hyperlink to the original source material, preferably a PDF \(e.g., court opinion or filing, legislation. Points should generally be well supported and should link to related content whenever possible. -## Style {#style} +## Style As an online program, Digest Comments have unique formatting requirements distinct from other legal journal writings. Below are some common items to check: @@ -19,21 +19,21 @@ As an online program, Digest Comments have unique formatting requirements distin * Do not hyphenate the following words: decisionmaker, factfinder * Italicize or bold for emphasis, as underlines look like a broken link. -## Commas {#commas} +## Commas When listing three or more things, separate each pair with a comma, including the last pair. The last comma precedes the coordinating conjunction \(e.g. _and_ or _or_\). > **Example:** Lions, tigers, and bears. -## Symbols {#symbols} +## Symbols Outside of citations, do not use "§" and "¶." Instead, always spell out and capitalize "Section" and "Paragraphs" in place of symbols. -## Quotations {#quotations} +## Quotations **Avoid block quotations to the extent possible.** You should be linking to sources, so there’s no need to quote in length. The exception to this rule, though, is the situation when you are analyzing statutory language; in that case, having the statute conveniently displayed in the body of the article is encouraged. -## Citations {#citations} +## Citations _Digest_ Comments need not follow Bluebook citation format. Indeed, you should cite sources primarily through hyperlink. Please archive your links to prevent linking to sources that later become unavailable. The Editing Team can also help out with this during the editing process. Please use \(recommended\) or to archive your links. diff --git a/notes/notecontributorguide.md b/notes/notecontributorguide.md index ec88033..4659c9c 100644 --- a/notes/notecontributorguide.md +++ b/notes/notecontributorguide.md @@ -10,7 +10,7 @@ You should make sure that your Note idea is not preempted; do some background re 1. Respond to suggestions from the [Note Editor](noteeditorguide.md). -## Requirements {#requirements} +## Requirements ### Novelty @@ -56,7 +56,7 @@ Please submit drafts as either .doc or .docx files. Label drafts in the followin > `contributor_name` `draft_version` `date_emailed` > **Example:** Fishwick First Draft 2017-06-30.doc -## Writing Process in a Nutshell {#nutshell} +## Writing Process in a Nutshell The process can be broken down into the following steps. @@ -65,13 +65,13 @@ The process can be broken down into the following steps. 3. [Second Draft](notecontributorguide.md#second) 4. [Submission](notecontributorguide.md#submission) -## Outline/Rough Draft {#outline} +## Outline/Rough Draft This is an opportunity for the Note Editor to provide feedback on the Note in the early stages of writing it, so that you can tailor, structure, and address issues. The outline/draft should be more than the proposal, and should reflect some research, but it needn’t be a complete article. The Note Editor should be available in case you have questions or would like help with the direction of the Note. There may be multiple back-and-forths with the Note Editor on the outline. This is ok: you want to minimize the number of major substantive edits once you start writing. -## First Draft {#first} +## First Draft **Your Tasks** @@ -98,7 +98,7 @@ If at any point the Note Editor has a question or concern regarding the Note or In between the first and second drafts, feel free to reach out to the Note Editor for any substantive or grammatical questions. The editing process for the second draft should adhere to the same guidelines as the editing process for the first draft. By the time the second draft is formally submitted, the Note should be organized and coherent. Most if not all sources should be found. -## Second Draft {#second} +## Second Draft **Your Tasks** @@ -118,7 +118,7 @@ If all the necessary changes are grammatical and there are only very minor subst If the Note requires substantial change, the Note Editor should email \[Submissions Editor email\] and joltdigest@mail.law.harvard.edu a copy of the Note and a description of these proposed major changes. The Digest Masthead will look at the Note and determine whether these major changes can be made in time for publication or if publication of the Note’s publication needs to be delayed. You should be working closely with the Note Editor throughout the editing process so that substantive changes will not be necessary at this point. -## Submission {#submission} +## Submission After both you and your Note Editor agree on the final draft, the Note Editor will email this finalized draft to diff --git a/notes/noteeditorguide.md b/notes/noteeditorguide.md index 76d947d..32dc238 100644 --- a/notes/noteeditorguide.md +++ b/notes/noteeditorguide.md @@ -22,7 +22,7 @@ You will help the Contributor meet the [requirements](notecontributorguide.md#re * review for substantive and grammatical errors. * ensure accurate citations. -## Editing Process in a Nutshell {#nutshell} +## Editing Process in a Nutshell The process can be broken down into the following steps. @@ -31,7 +31,7 @@ The process can be broken down into the following steps. 3. [Second Draft](noteeditorguide.md#second) 4. [Submission](noteeditorguide.md#submission) -## Outline/Rough Draft {#outline} +## Outline/Rough Draft After proposing a writing topic, the Contributor will email an outline for you to review. While the outline should be more than the initial proposal---reflecting some research---it need not be a complete draft. @@ -44,7 +44,7 @@ Aim to provide substantive feedback on the outline before the Contributor starts You should be available to field the Contributor's questions throughout the process but especially in the beginning. There may be multiple iterations of the outline. Focus on the substance and aim to minimize the number of major substantive edits you and the Contributor will have to make on the drafts. -## First Draft {#first} +## First Draft The Contributor will email you the first draft in a Microsoft Word Document format. You will have **one week** to review the Note. You should @@ -60,7 +60,7 @@ Name the marked-up draft document in the following manner. Afterwards, email the marked-up draft to the Contributor and CC the \[Submissions Editor\] and joltdigest@mail.law.harvard.edu. -## Second Draft {#second} +## Second Draft In between the first and second drafts, you should be available to the Contributor for any substantive or grammatical questions. The editing process for the second draft should adhere to the same guidelines as that for the first draft. By the time the second draft is formally submitted, the Note should be organized and coherent. @@ -70,7 +70,7 @@ Once you receives the second draft, your next step is dependent on what changes If major substantive changes need to be made to the Note at this point, you should email the \[Submissions Editor\] and joltdigest@mail.law.harvard.edu a copy of the Note and a description of these proposed major changes. The _Digest_ Masthead will look at the Note and determine whether these major changes can be made in time for publication or if publication of the Note’s publication needs to be delayed. -## Submission {#submission} +## Submission Once you and the Contributor agree on the final draft, email it to diff --git a/notes/notestylecitation/README.md b/notes/notestylecitation/README.md index 5107c8d..806a3d4 100644 --- a/notes/notestylecitation/README.md +++ b/notes/notestylecitation/README.md @@ -4,15 +4,15 @@ _Digest_ Notes are JOLT Student Notes adapted for the online medium. This means you will need to follow the style and citation rigor expected in a Law Journal Note, subject to a few adaptions for it being posted online. -## Requirements {#req} +## Requirements Follow The Bluebook \(20th Edition\) whitepages where its rules do not directly conflict with the rules laid out here. -## Organization {#org} +## Organization Use section headings to separate your Note into digestable parts. Do not precede your section headings with any counters \(e.g. Roman Numerals, Arabic Numerals, Letters, etc.\). Do not use subsections. -## Citations {#citations} +## Citations Provide a citation for every statement that is not your original idea. @@ -20,7 +20,7 @@ As _Digest_ Notes are not paginated, do not use footnotes. Your citations will, But keep in mind that Readers will rarely refer to endnotes. As such, try to tailor endnotes to contain only citations. To convey helpful but nonessential information, consider placing them in in-text parentheticals or cutting them out entirely. -## Style {#style} +## Style Since Digest is available online, some formatting preferences may be different, so this Digest citation guide supersedes the generic JOLT Style Guide. Below are some common items to check: @@ -35,11 +35,11 @@ There are also some additional requirements specific to a _Digest_ Note: * Use only _italics_ for formatting emphasis \(not bold or underline\). * Do not use small-caps. -## Commas {#commas} +## Commas Use the serial comma. Read [here](../../reports/reportstylecitation.md#commas) for more information. -## Symbols {#symbols} +## Symbols Outside of citations, do not use "§" and "¶." Instead, always spell out and capitalize "Section" and "Paragraphs" in place of symbols. diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md index b07ba5f..3956d0b 100644 --- a/reports/reportcontributorguide.md +++ b/reports/reportcontributorguide.md @@ -17,7 +17,7 @@ Subject Matter Coordinators \(SMCs\) are constantly looking for cutting edge dev Unless otherwise noted, all of the following communications are designed to \(and should\) occur via email. -## Step 1: Getting Started {#step1} +## Step 1: Getting Started You, the _Digest_ Contributor, will be assigned reports according to the availability and subject matter preferences you submitted in the sign-up survey. SMCs will simultaneously assign Report Editors and Contributors to a topic. Unless your Coordinator specified otherwise, you will have **four days** to finish a draft. @@ -97,7 +97,7 @@ After receiving your assignment from the Subject Matter Coordinator \(SMC\), imm If you simply cannot write the report within the required time, please let the SMC know as soon as possible so the SMC can find another Contributor. Note that you may not have the opportunity to write a Digest report at a later time. -## Step 3: Drafting the Report {#step3} +## Step 3: Drafting the Report The purpose of _Digest_ reports is to provide a relatively brief and ideologically-neutral overview of their subject. @@ -166,10 +166,6 @@ Examples can be found [here](http://jolt.law.harvard.edu/digest/doj-v-bmi-doj-ar > The \[insert hyperlink\] provides an overview of the case. \[insert hyperlink to commentary\] criticizes the decision \[insert one-phrase summary of criticism\]. \[Insert brief 2–4 sentence discussion of why case is significant \(if known\)\] {% endtab %} -{% tab title="" %} - -{% endtab %} - {% tab title="Sample Legislation Report" %} See [example](https://jolt.law.harvard.edu/digest/coalition-of-32-state-ags-outline-opposition-to-federal-preemption-of-state-data-breach-notification-laws). @@ -193,7 +189,7 @@ See [example](https://jolt.law.harvard.edu/digest/coalition-of-32-state-ags-outl {% endtab %} {% endtabs %} -## Step 4: Forwarding the Report {#step4} +## Step 4: Forwarding the Report {% hint style="success" %} #### Your Responsibilities diff --git a/reports/reporteditorguide.md b/reports/reporteditorguide.md index 5e0c938..e1f8a87 100644 --- a/reports/reporteditorguide.md +++ b/reports/reporteditorguide.md @@ -15,23 +15,23 @@ Subject Matter Coordinators \(SMCs\) are constantly looking for “hot” law & * [Step 4](reporteditorguide.md#step5): Moving the Report Forward {% endhint %} -## Step 1: Getting Started {#step1} +## Step 1: Getting Started You, the _Digest_ Report Editor, is tasked with reviewing the Contributor's draft for substantive and technical accuracy. You will usually have about three days after the Contributor has shared the first draft to give comments and suggestions. You'll be working with the Contributor in finalizing the draft before the Contributor hands it off to the SMC and Digest Submissions Editor \(Wendy Chu\) for a final review and publication. In the event you are unable to complete an assignment, please notify the assigning Coordinator immediately. If your availability changes during the year, notify the [Digest Executive Editor](https://jolt.law.harvard.edu/masthead). -## Step 2: Receiving and Confirming Receipt of Your Assignment {#step2} +## Step 2: Receiving and Confirming Receipt of Your Assignment Please see [Step 2 in the Contributor's Guide](reportcontributorguide.md#step-2-receiving-and-confirming-receipt-of-your-assignment). -## Step 3: Editing {#step4} +## Step 3: Editing As an Report Editor, you will work with the Contributor to ensure the report is publication-ready. You should make sure that the Contributor's piece follows the [Style & Citations Guide](reportstylecitation.md) and comply with the recommendations laid out in [Step 3 of the Contributor's Guide](reportcontributorguide.md#step3). Enter your edits directly into the Google Docs in ["Suggest Edits" mode](https://support.google.com/docs/answer/6033474?co=GENIE.Platform%3DDesktop&hl=en). -## Step 4: Moving the Report Forward {#step5} +## Step 4: Moving the Report Forward The Contributor will have shared in the assigning email thread the link to the Google Doc containing the draft \(see [Step 4 of the Contributor's Guide](reportcontributorguide.md#step4) for more details\). Make your comments and suggestions directly within the Google Doc. Once you're done with your comments and suggestions, reply all in the assigning email threads letting everyone know \(1\) a summary of your edits; and \(2\) any questions/concerns that arose during editing. diff --git a/reports/reportstylecitation.md b/reports/reportstylecitation.md index 2d91981..9d62601 100644 --- a/reports/reportstylecitation.md +++ b/reports/reportstylecitation.md @@ -2,7 +2,7 @@ Digest Reports are brief summaries of important developments in law and technology. The purpose of Digests Reports is to break down complex legal and technical issues for readers who may not be familiar with the topic. The Digest Reports also serve to keep attorneys who practice within the field of Internet and technology law apprised of new precedent or legislation. -## Requirements {#requirements} +## Requirements **All** articles should hyperlink to the original source material, preferably a PDF \(e.g., court opinion or filing, legislation\). Additionally, we recommend that all articles should have at least 2 hyperlinks to related material and/or commentary. They can include: @@ -12,7 +12,7 @@ Digest Reports are brief summaries of important developments in law and technolo Contributions should pull from a variety of sources and should be more than just reiterations of existing commentary or reporting. The 2-link minimum is exactly that – a minimum. Points should generally be well supported and should link to related content whenever possible. -## Style {#style} +## Style Since Digest is available online, some formatting preferences may be different, so this Digest citation guide supersedes the generic JOLT Style Guide. Below are some common items to check: @@ -23,23 +23,23 @@ Since Digest is available online, some formatting preferences may be different, * Do not hyphenate the following words: decisionmaker, factfinder * Do not use underlining for emphasis. This can easily be mistaken for a broken link. -## Commas {#commas} +## Commas When listing three or more things, separate each pair with a comma, including the last pair. The last comma precedes the coordinating conjunction \(e.g. _and_ or _or_\). > **Example:** Lions, tigers, and bears. -## Symbols {#symbols} +## Symbols Outside of citations, do not use "§" and "¶." Instead, spell out and capitalize "Section" and "Paragraphs" in place of symbols. -## Quotations {#quotations} +## Quotations If you are quoting a source, make sure to review the Bluebook Rule 5: Quotations for formatting, alterations, internal quotations, and omissions. **Block Quotes** — avoid them. You’ll already be linking the reader to the source so there’s no need to quote in length. The exception to this rule, though, is the situation when you are analyzing statutory language; in that case, having the statute conveniently displayed in the body of the article is encouraged. -## Citations {#citations} +## Citations Despite the Digest’s more informal style, we strive to maintain the high standards for JOLT student writing by citing sources consistently. @@ -123,7 +123,7 @@ If a PDF of a court document is available through an open access online source \ > **Example:** Complaint for Declaratory Judgment and Injunctive Relief, GoldieBlox, Inc. v. Island Def Jam Music Group, A Div. of UMG Recordings, Inc., No. 3:13-cv-05428 \(N.D. Cal. Nov. 21, 2013\), [complaint](http://www.scribd.com/doc/186402972/Beastie) hosted by Scribd. > **Not:** Viacom Int’l Inc. v. YouTube, Inc., No. 07 Civ. 2103 \(S.D.N.Y. June 23, 2010\), [slip op.](https://cases.justia.com/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf) hosted by Justia.com -## Substance {#substance} +## Substance Keep in mind that the value of _Digest_ depends heavily on its accuracy. Please check your piece against the following guidelines **before** submitting the draft. @@ -173,7 +173,7 @@ Keep in mind that the value of _Digest_ depends heavily on its accuracy. Please **Links** -- check that all your hyperlinks point to the correct site and that all sources or mentioned cases or legislation are hyperlinked where possible. -## Locating Relevant Material and Commentary {#relevant} +## Locating Relevant Material and Commentary Reports should hyperlink to the original source material \(e.g., court opinion or filing, legislation\). In addition, all reports should have **at least** 2 hyperlinks to related materials and/or commentary. They can include: From d2031972e35c702e803fcee25253a6d384d02fe1 Mon Sep 17 00:00:00 2001 From: Alicia Loh Date: Fri, 13 Sep 2019 22:41:28 +0000 Subject: [PATCH 04/11] GitBook: [2.0.0] 4 pages modified --- README.md | 32 +++++++++------ SUMMARY.md | 3 +- about-us.md | 14 +++++++ reports/reportcontributorguide.md | 67 ++++++++++++++++++++++--------- 4 files changed, 83 insertions(+), 33 deletions(-) create mode 100644 about-us.md diff --git a/README.md b/README.md index 3a4a09e..ef32d55 100644 --- a/README.md +++ b/README.md @@ -1,26 +1,32 @@ -# FAQ +# About Us -## What is JOLT _Digest_? +## What is JOLT Digest? -The [_JOLT Digest_](http://jolt.law.harvard.edu/digest) is the online companion to the Harvard Journal of Law & Technology \([JOLT](http://jolt.law.harvard.edu/)\). It is intended to serve as a one-stop source of legal news to professors, practitioners, law students, and the general public on issues at the intersection of law and technology. +[JOLT Digest](http://jolt.law.harvard.edu/digest) is the online companion to the Harvard Journal of Law & Technology \([JOLT](http://jolt.law.harvard.edu/)\). It is intended to serve as a one-stop source of legal news to professors, practitioners, law students, and the general public on issues at the intersection of law and technology. -The Digest features short articles on new, precedential, or interesting cases; new legislation; administrative developments of note; and other interesting happenings. By applying JOLT’s traditionally high editing standards to the Digest, we create a uniquely useful and trustworthy resource. +Digest features short articles on new, precedential, or interesting cases; new legislation; administrative developments of note; and other interesting happenings. By applying JOLT’s traditionally high editing standards to the Digest, we create a uniquely useful and trustworthy resource. -## Do you conform with the Oxford Comma? +## Meet the team! -Yes. Read more [here](reports/reportstylecitation.md#commas). +**Digest Executive Editor** \(Mindy Nam\) supervises the entire Digest team, creates the Digest publication schedule, and provides an additional layer of editing for all publications. -## Meet the editing team! +**Digest Reports Editor** \(Alicia Loh\) oversees all Digest Reports: assisting the SMCs to generate topics and schedule assignments, coordinating the assignment process, and providing a final layer of editing. -**Contributors** write the Report articles for _JOLT Digest_ and also suggest sources of online commentary that can be linked from Digest articles. +**Subject Matter Coordinators \(SMCs\)** \(Sam Santopaolo, Justin Fishman, and Andrew Distell\) assign topics to and work closely with Contributors and Report Editors on their subject matter teams to publish Digest Reports. -**Report Editors** supervise the Contributors. Report Editors are responsible for editing article drafts and adding additional relevant materials. +**Report Contributors** and **Editors** work together to publish Digest Reports that provide overviews on important new developments in law and technology. -**Subject Matter Coordinators** \(Mindy Nam and Stella Mao\) assign topics to Contributors and Report Editors on their subject matter teams. Assignments include the topic and links to sources that help Contributors to understand the issue and links to relevant online commentary. +**Digest Content Editors** \(Or-el Vaknin and Anita Liu\) take the lead on seeing Digest Student Notes and Comments from submission to publication. This involves back-and-forth on substantive edits with the authors to make sure their pieces meet Digest standards. -**Digest Content Editors** \(Brian Kulp and Phillip Takhar\) take the lead on seeing Digest Student Notes and Comments from submission to publication. This involves back-and-forth on substantive edits with the authors to make sure their pieces meet Digest standards. +**Digest Development Manager** \(Alexandra Mushka\) reaches out to professors, practitioners, and non-HLS law students to grow the JOLT Digest community. -**Digest Submissions Editor** \(Wendy Chu\) oversees and assists the Coordinators to generate topics and schedule assignments, coordinates the assignment process, provides a final layer of editing for entries, upload posts into WordPress, and ensure that the entries remain up-to-date as new developments occur. +**Federal Circuit Panel Writers** \(Hye Yoon Hwang, Meera Midha, Kaye Horstman, and Will Czaplyski\) write Notes on current issues in the Federal Circuit. -**Digest Executive Editor** \(Peter Zhu\) supervises the Digest Content Editor and other Digest team members, creates the Digest publication schedule, and provides an additional layer of editing for entries. +**Podcast Content Team** \(Flora Wang, Minnie Che, Nick Berk, and Oladeji Tiamiyu\) leads the creation of podcast episodes and researches the subject material. + +**Podcast Production Team** \(Nick Curry and Bowen Wang\) record and edit each episode. + +\*\*\*\* + +\*\*\*\* diff --git a/SUMMARY.md b/SUMMARY.md index 5acd964..9877f2b 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -1,6 +1,7 @@ # Table of contents -* [FAQ](README.md) +* [About Us](README.md) +* [FAQ](about-us.md) ## Reports diff --git a/about-us.md b/about-us.md new file mode 100644 index 0000000..aeb277d --- /dev/null +++ b/about-us.md @@ -0,0 +1,14 @@ +# FAQ + +## How can I get involved with Digest? + +Fill in information here + +## What is the difference between Reports, Notes, and Commentary? + +Fill in information here + +## Do you conform with the Oxford Comma? + +Yes. Read more [here](reports/reportstylecitation.md#commas). + diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md index 3956d0b..ac21be4 100644 --- a/reports/reportcontributorguide.md +++ b/reports/reportcontributorguide.md @@ -2,9 +2,9 @@ ## Welcome to the Report Contributor's Guide! -This guide will provide an overview of your responsibilities as a **Contributor** of a _**Digest**_ **Report**. Reports are short objective overviews, 500-700 words in length, of recent court opinions or pieces of legislation. They also provide links to primary sources and additional commentary for readers who want to dig deeper. +This guide will provide an overview of your responsibilities as a **Contributor** of a **Digest Report**. Reports are short objective overviews, 500-700 words in length, of recent court opinions or pieces of legislation. They also provide links to primary sources and additional commentary for readers who want to dig deeper. -Subject Matter Coordinators \(SMCs\) are constantly looking for cutting edge developments in law & technology. They will assign the topic to you and an Report Editor. Your job is to write the substantive content of the report while the Report Editor will help you ensure it is publication-ready. +Subject Matter Coordinators \(SMCs\) are constantly looking for cutting edge developments in law & technology. They will assign the topic to you and a Report Editor. Your job is to write the substantive content of the report while the Report Editor will help you ensure it is publication-ready. {% hint style="info" %} ### Writing Process in a Nutshell @@ -12,16 +12,23 @@ Subject Matter Coordinators \(SMCs\) are constantly looking for cutting edge dev * [Step 1](reportcontributorguide.md#step1): Getting Started * [Step 2](reportcontributorguide.md#step2): Receiving and Confirming Receipt of Your Assignment * [Step 3](reportcontributorguide.md#step3): Drafting the Report -* [Step 4](reportcontributorguide.md#step4): Forwarding the Report & Following Up +* [Step 4](reportcontributorguide.md#step4): Edits to the Report +* [Step 5](https://jolt.gitbook.io/jolt-digest-citation-and-style-guide/reports/reportcontributorguide#step5): Feedback {% endhint %} Unless otherwise noted, all of the following communications are designed to \(and should\) occur via email. ## Step 1: Getting Started -You, the _Digest_ Contributor, will be assigned reports according to the availability and subject matter preferences you submitted in the sign-up survey. SMCs will simultaneously assign Report Editors and Contributors to a topic. Unless your Coordinator specified otherwise, you will have **four days** to finish a draft. +You, the Digest Contributor, will be assigned reports according to the availability and subject matter preferences you submitted in the sign-up survey. SMCs will simultaneously assign Report Editors and Contributors to a topic. -If you are unable to complete an assignment, please notify the assigning SMC immediately. If your availability changes during the year, notify the Digest Executive Editor. +Here's what the editing timeline will look like \(unless otherwise stated\): + +* **Sunday Night**: ****SMC will send the assigning email +* **Thursday by 11:59pm**: ****Contributor finishes draft report +* **Saturday by noon**: ****Editor submits all edits +* **Sunday by noon**: Contributor finalizes changes +* **Monday**: SMC and Digest Reports Editor makes final edits, and Report is published ## Step 2: Receiving and Confirming Receipt of Your Assignment @@ -30,15 +37,16 @@ If you are unable to complete an assignment, please notify the assigning SMC imm The SMC will send you and the Report Editor an assigning email with: 1. Name of your Contributor and Editor -2. Draft due date +2. Draft due date and editing timeline 3. Report topic 1. Background \(parties, procedural posture, etc.\) 2. Significance of the case/legislation 3. Link or attachment to primary source -4. Link to [Contributor](reportcontributorguide.md#welcome-to-the-report-contributors-guide), [Editor](reporteditorguide.md#welcome-to-the-report-editors-guide), and [Style & Citation Guide](reportstylecitation.md) + 4. What to do if you want to choose a different topic +4. Link to [Contributor](reportcontributorguide.md#welcome-to-the-report-contributors-guide), [Editor](reporteditorguide.md#welcome-to-the-report-editors-guide), and [Style & Citation Guides](reportstylecitation.md) 5. Credentials for online Bluebook access -If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Executive Editor, who are also available to answer questions. +If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Reports Editor, who is also available to answer questions. {% endtab %} {% tab title="Sample Email" %} @@ -52,9 +60,9 @@ Please reply all to this email and confirm that you are able to take on this wee **Assignment:** summarize Aatrix Software, Inc. v. Green Shades Software, Inc., No. 2017-1452, 2018 WL 843288 \(Fed. Cir. Feb. 14, 2018\) along with links to at least two outside sources. You can find examples of posts at [https://jolt.law.harvard.edu/digest/category/?cat=patent](https://jolt.law.harvard.edu/digest/category/?cat=patent). -**Draft Deadline** \(Contributor send draft to me and Editor\): 11:59 p.m. Wed, Feb 21. +**Draft Deadline** \(Contributor send draft to me and Editor\): 11:59 pm on Thursday, Feb 21. -**Edits Deadline** \(Editor send marked up draft to me and Contributor\): 11:59 p.m. Sat, Feb 24. +**Edits Deadline** \(Editor send marked up draft to me and Contributor\): noon on Sat, Feb 24. Thanks for writing for Digest this semester! According to the Fall 2017 Report Schedule, <**Contributor**>, you have been assigned the role of Digest Contributor for this week. **<Editor>**, you are assigned the role or Report Editor. @@ -97,9 +105,17 @@ After receiving your assignment from the Subject Matter Coordinator \(SMC\), imm If you simply cannot write the report within the required time, please let the SMC know as soon as possible so the SMC can find another Contributor. Note that you may not have the opportunity to write a Digest report at a later time. +{% hint style="warning" %} +**Want to choose a different topic?** + +**Please let your SMC know within 24 hours of receiving your assignment.** A Report topic should be timely and related to law and technology. + +Please include a link to the primary source and at least two links to other commentary on the topic in your email to your SMC. The SMC reserves the right to reject unsuitable topics. +{% endhint %} + ## Step 3: Drafting the Report -The purpose of _Digest_ reports is to provide a relatively brief and ideologically-neutral overview of their subject. +The purpose of Digest Reports is to provide a relatively brief and ideologically-neutral overview of their subject. {% hint style="success" %} #### Your Responsibilities @@ -117,9 +133,9 @@ As a Contributor, you are responsible for the technical and substantive accuracy 2. How to format citations 3. Style guidelines -**Please be very careful** not to overstate or misrepresent the source. Digest Reports are often on the first page of Google inquiries for cutting-edge cases -- getting it wrong has consequences. If you are unsure how to summarize a particular point, please ask for help. If all else fails, consider paraphrasing or quoting the source. +**Please be very careful** not to overstate or misrepresent the source. Digest Reports are often on the first page of Google inquiries for cutting-edge cases — getting it wrong has consequences. If you are unsure how to summarize a particular point, please ask for help. If all else fails, consider paraphrasing or quoting the source. -Visit [_Digest_](https://jolt.law.harvard.edu/digest/category/?cat=reports) for examples of edited reports. [Here](http://jolt.law.harvard.edu/digest/federal-circuit-flash-digest-basf-corp-v-johnson-matthey-inc) are [several](http://jolt.law.harvard.edu/digest/teva-v-eli-lilly-teva-argues-lilly-is-infringing-migraine-drug-patent-in-the-united-states) [examples](http://jolt.law.harvard.edu/digest/ubers-august-settlement-with-the-ftc-and-new-data-insecurity-revelations). +Visit [Digest](https://jolt.law.harvard.edu/digest/category/?cat=reports) for examples of edited reports. [Here](http://jolt.law.harvard.edu/digest/federal-circuit-flash-digest-basf-corp-v-johnson-matthey-inc) are [several](http://jolt.law.harvard.edu/digest/teva-v-eli-lilly-teva-argues-lilly-is-infringing-migraine-drug-patent-in-the-united-states) [examples](http://jolt.law.harvard.edu/digest/ubers-august-settlement-with-the-ftc-and-new-data-insecurity-revelations). **Length** - while the report’s length will vary with the complexity of the subject, generally the report should be no longer than 500–700 words. The purpose of the report is to provide an accurate overview of the most important aspects of the subject. Readers interested in further detail can visit the primary and secondary sources that will be included. @@ -189,7 +205,7 @@ See [example](https://jolt.law.harvard.edu/digest/coalition-of-32-state-ags-outl {% endtab %} {% endtabs %} -## Step 4: Forwarding the Report +## Step 4: Edits to the Report {% hint style="success" %} #### Your Responsibilities @@ -197,20 +213,33 @@ See [example](https://jolt.law.harvard.edu/digest/coalition-of-32-state-ags-outl 1. Comment sections of your Report that you believe need a closer review 2. Share your draft on Google Doc 3. Work with the Editor to finalize the piece -4. Be available for any follow-up edits from the Subject Matter Coordinator +4. Be available for any follow-up edits from the Subject Matter Coordinator {% endhint %} Please share your draft on Google Doc with the following: * Report Editor * Assigning Subject Matter Coordinator -* Digest Executive Editor \(joltdigest@mail.law.harvard.edu\) +* Digest Account \(joltdigest@mail.law.harvard.edu\) -The easiest way to do this is to share a link in the assigning email thread. The Editor will have about three days to add comments and suggestions in the Google Doc. Please review them, finalize the draft, and notify the assigning SMC \(via the email thread\). The SMC will take one last look and may offer an additional round of comments to be reviewed before sending it to production. +The easiest way to do this is to share a link in the assigning email thread. The Editor will have about three days to add comments and suggestions in the Google Doc. Please review them, finalize the draft, and notify the assigning SMC \(via the email thread\). The SMC will take one last look and may offer an additional round of comments to be reviewed. You and the Editor will be asked to look over the Report one last time before it is published. -Expect a follow-up email from the SMC once your piece goes live. +## Step 5: Feedback + +{% hint style="warning" %} +**You must fill out the feedback form to receive substantive feedback on your writing.** +{% endhint %} + +After the Report is published online, you will get an email from the Digest Reports Editor with a link and a feedback form. We ask for your feedback on: + +1. Your experience writing the Report \(to help us improve the process\) +2. Your experience working with the SMC and Editor \(to help us make promotion decisions\) + +We also provide the opportunity to give **anonymous** feedback to your Editor. The Digest Reports Editor will combine their feedback with your feedback and the SMC's. The feedback you receive will be similarly anonymized. ## Thank you! -The _JOLT Digest_ team thanks you for the time you will be putting into creating Digest content. We hope you enjoy the content creation process and working with the subject matter of your assignments. Please feel free to email the [_Digest Masthead_](https://jolt.law.harvard.edu/masthead) if you have any concerns or suggestions on improving the process! +The JOLT Digest team thanks you for the time you will be putting into creating Digest content. We hope you enjoy the content creation process and working with the subject matter of your assignments. + +Follow the JOLT [Twitter](https://www.twitter.com/harvardjolt) or [Facebook Page](https://www.facebook.com/harvardjolt) to stay up to date on all Digest publications! From 1b3a51e682568188703c5b1532ee5bbec7be44c3 Mon Sep 17 00:00:00 2001 From: Alicia Loh Date: Fri, 13 Sep 2019 22:59:22 +0000 Subject: [PATCH 05/11] GitBook: [2.0.0] 2 pages modified --- reports/reportcontributorguide.md | 10 +++++----- reports/reporteditorguide.md | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md index ac21be4..f15066f 100644 --- a/reports/reportcontributorguide.md +++ b/reports/reportcontributorguide.md @@ -20,7 +20,7 @@ Unless otherwise noted, all of the following communications are designed to \(an ## Step 1: Getting Started -You, the Digest Contributor, will be assigned reports according to the availability and subject matter preferences you submitted in the sign-up survey. SMCs will simultaneously assign Report Editors and Contributors to a topic. +You, the Digest Contributor, will be assigned reports according to the availability and subject matter preferences you submitted in the sign-up survey. SMCs will simultaneously assign Report Editors and Contributors to a topic. Here's what the editing timeline will look like \(unless otherwise stated\): @@ -106,11 +106,11 @@ After receiving your assignment from the Subject Matter Coordinator \(SMC\), imm If you simply cannot write the report within the required time, please let the SMC know as soon as possible so the SMC can find another Contributor. Note that you may not have the opportunity to write a Digest report at a later time. {% hint style="warning" %} -**Want to choose a different topic?** +**Want to choose a different topic?** -**Please let your SMC know within 24 hours of receiving your assignment.** A Report topic should be timely and related to law and technology. +**Please let your SMC know within 24 hours of receiving your assignment.** A Report topic should be timely and related to law and technology. -Please include a link to the primary source and at least two links to other commentary on the topic in your email to your SMC. The SMC reserves the right to reject unsuitable topics. +Please include a link to the primary source and at least two links to other commentary on the topic in your email to your SMC. The SMC reserves the right to reject unsuitable topics. {% endhint %} ## Step 3: Drafting the Report @@ -222,7 +222,7 @@ Please share your draft on Google Doc with the following: * Assigning Subject Matter Coordinator * Digest Account \(joltdigest@mail.law.harvard.edu\) -The easiest way to do this is to share a link in the assigning email thread. The Editor will have about three days to add comments and suggestions in the Google Doc. Please review them, finalize the draft, and notify the assigning SMC \(via the email thread\). The SMC will take one last look and may offer an additional round of comments to be reviewed. You and the Editor will be asked to look over the Report one last time before it is published. +The easiest way to do this is to share a link in the assigning email thread. The Editor will have about three days to add comments and suggestions in the Google Doc. Please review them, finalize the draft, and notify the assigning SMC \(via the email thread\). The SMC will take another look and may offer an additional round of edits. You and the Editor will be asked to review the Report one last time before it is published. ## Step 5: Feedback diff --git a/reports/reporteditorguide.md b/reports/reporteditorguide.md index e1f8a87..b7f636d 100644 --- a/reports/reporteditorguide.md +++ b/reports/reporteditorguide.md @@ -17,7 +17,7 @@ Subject Matter Coordinators \(SMCs\) are constantly looking for “hot” law & ## Step 1: Getting Started -You, the _Digest_ Report Editor, is tasked with reviewing the Contributor's draft for substantive and technical accuracy. You will usually have about three days after the Contributor has shared the first draft to give comments and suggestions. You'll be working with the Contributor in finalizing the draft before the Contributor hands it off to the SMC and Digest Submissions Editor \(Wendy Chu\) for a final review and publication. +You, the _Digest_ Report Editor, is tasked with reviewing the Contributor's draft for substantive and technical accuracy. You will usually have about two days after the Contributor has shared the first draft to give comments and suggestions. You'll be working with the Contributor in finalizing the draft before the Contributor hands it off to the SMC and Digest Submissions Editor \(Wendy Chu\) for a final review and publication. In the event you are unable to complete an assignment, please notify the assigning Coordinator immediately. If your availability changes during the year, notify the [Digest Executive Editor](https://jolt.law.harvard.edu/masthead). From dc611ce8be9e31f43893ea0afb90422432010083 Mon Sep 17 00:00:00 2001 From: Alicia Loh Date: Sat, 14 Sep 2019 03:30:57 +0000 Subject: [PATCH 06/11] GitBook: [2.0.0] 3 pages modified --- about-us.md | 18 ++++- reports/reportcontributorguide.md | 4 +- reports/reporteditorguide.md | 118 +++++++++++++++++++++++++++--- 3 files changed, 126 insertions(+), 14 deletions(-) diff --git a/about-us.md b/about-us.md index aeb277d..e92275c 100644 --- a/about-us.md +++ b/about-us.md @@ -2,11 +2,23 @@ ## How can I get involved with Digest? -Fill in information here +**Harvard Law Students** can write Reports, Notes, or Commentary. Sign up to write or edit a Report at the beginning of each semester. Join the [JOLT mailing list](https://test.us9.list-manage.com/subscribe?u=fd5e177723c7929c4cc46bab1&id=dacf20620a) to know when to sign up. -## What is the difference between Reports, Notes, and Commentary? +**Other Law Students and Recent Graduates** can write Notes or Comments. -Fill in information here +**Academics, Practitioners, and Other Professionals** can write Comments. + +We accept submissions for Notes and Comments all year round. Please fill out [this form](https://forms.gle/mC9Tw2sRYxHjA2JV9), and we will contact you. + +If you have any questions, please email joltdigest@mail.law.harvard.edu. + +## What is the difference between Reports, Notes, and Comments? + +**Reports** are short objective overviews, 500–700 words in length, of recent court opinions or pieces of legislation. + +**Notes** provide a novel analysis on an issue related to law and technology. These are formal pieces that include Bluebooked citations and published in PDF format. They are comparable to JOLT's print publication student notes but shorter in length \(1,500–2,000 words for a Digest note, 4,000–6,000 words for a print note\). + +**Comments** are about 2,000 words and can come in several general forms: opinion pieces, primers, or responses. They allow the author to participate in ongoing discussions about cutting-edge legal issues without the formality of our Notes or the impartiality of our Reports. ## Do you conform with the Oxford Comma? diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md index f15066f..2695151 100644 --- a/reports/reportcontributorguide.md +++ b/reports/reportcontributorguide.md @@ -2,7 +2,7 @@ ## Welcome to the Report Contributor's Guide! -This guide will provide an overview of your responsibilities as a **Contributor** of a **Digest Report**. Reports are short objective overviews, 500-700 words in length, of recent court opinions or pieces of legislation. They also provide links to primary sources and additional commentary for readers who want to dig deeper. +This guide will provide an overview of your responsibilities as a **Contributor** of a **Digest Report**. Reports are short objective overviews, 500–700 words in length, of recent court opinions or pieces of legislation. They also provide links to primary sources and additional commentary for readers who want to dig deeper. Subject Matter Coordinators \(SMCs\) are constantly looking for cutting edge developments in law & technology. They will assign the topic to you and a Report Editor. Your job is to write the substantive content of the report while the Report Editor will help you ensure it is publication-ready. @@ -127,7 +127,7 @@ The purpose of Digest Reports is to provide a relatively brief and ideologically {% tabs %} {% tab title="Instructions" %} -As a Contributor, you are responsible for the technical and substantive accuracy of the report. Refer to the [Citation, Style, and Substance Guide](reportstylecitation.md) for: +As a Contributor, you are responsible for the technical and substantive accuracy of the report. Refer to the [Style & Citations Guide](reportstylecitation.md) for: 1. What to look for in a case or legislation 2. How to format citations diff --git a/reports/reporteditorguide.md b/reports/reporteditorguide.md index b7f636d..114e9a7 100644 --- a/reports/reporteditorguide.md +++ b/reports/reporteditorguide.md @@ -2,38 +2,138 @@ ## Welcome to the Report Editor's Guide! -This guide will provide an overview of your responsibilities as a **Editor** of a _**Digest**_ **Report**. Reports are short, objective overviews, 500-700 words in length, of recent court opinions or pieces of legislation. They also provide links to primary sources and additional commentary for readers who want to dig deeper. +This guide will provide an overview of your responsibilities as a **Editor** of a **Digest Report**. Reports are short, objective overviews, 500–700 words in length, of recent court opinions or pieces of legislation. They also provide links to primary sources and additional commentary for readers who want to dig deeper. -Subject Matter Coordinators \(SMCs\) are constantly looking for “hot” law & technology news. They will assign the topic to you and an Report Editor. Your job as the Report Editor is to ensure it is publication-ready. +Subject Matter Coordinators \(SMCs\) are constantly looking for “hot” law & technology news. They will assign the topic to you and a Report Contributor. Your job as the Report Editor is to ensure it is publication-ready. {% hint style="info" %} ## Editing Process in a Nutshell * [Step 1](reporteditorguide.md#step1): Getting Started -* [Step 2](reporteditorguide.md#step2): Receiving AND Confirming Receipt of Your Assignment +* [Step 2](reporteditorguide.md#step2): Receiving and Confirming Receipt of Your Assignment * [Step 3](reporteditorguide.md#step4): Editing * [Step 4](reporteditorguide.md#step5): Moving the Report Forward +* [Step 5](https://jolt.gitbook.io/jolt-digest-citation-and-style-guide/reports/reporteditorguide#step5): Feedback {% endhint %} ## Step 1: Getting Started -You, the _Digest_ Report Editor, is tasked with reviewing the Contributor's draft for substantive and technical accuracy. You will usually have about two days after the Contributor has shared the first draft to give comments and suggestions. You'll be working with the Contributor in finalizing the draft before the Contributor hands it off to the SMC and Digest Submissions Editor \(Wendy Chu\) for a final review and publication. +You, the Report Editor, are tasked with reviewing the Contributor's draft for substantive and technical accuracy. You will usually have about two days after the Contributor has shared the first draft to give comments and suggestions. You'll be working with the Contributor in finalizing the draft before handing it off to the SMC and Digest Reports Editor \(Alicia Loh\) for a final review and publication. -In the event you are unable to complete an assignment, please notify the assigning Coordinator immediately. If your availability changes during the year, notify the [Digest Executive Editor](https://jolt.law.harvard.edu/masthead). +Here's what the editing timeline will look like \(unless otherwise stated\): + +* **Sunday Night**: ****SMC will send the assigning email +* **Thursday by 11:59pm**: ****Contributor finishes draft report +* **Saturday by noon**: ****Editor submits all edits +* **Sunday by noon**: Contributor finalizes changes +* **Monday**: SMC and Digest Reports Editor makes final edits, and Report is published ## Step 2: Receiving and Confirming Receipt of Your Assignment -Please see [Step 2 in the Contributor's Guide](reportcontributorguide.md#step-2-receiving-and-confirming-receipt-of-your-assignment). +{% tabs %} +{% tab title="Instructions" %} +The SMC will send you and the Contributor an assigning email with: + +1. Name of your Contributor and Editor +2. Draft due date and editing timeline +3. Report topic + 1. Background \(parties, procedural posture, etc.\) + 2. Significance of the case/legislation + 3. Link or attachment to primary source + 4. What to do if you want to choose a different topic +4. Link to [Contributor](reportcontributorguide.md#welcome-to-the-report-contributors-guide), [Editor](reporteditorguide.md#welcome-to-the-report-editors-guide), and [Style & Citation Guides](reportstylecitation.md) +5. Credentials for online Bluebook access + +If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Reports Editor, who is also available to answer questions. +{% endtab %} + +{% tab title="Sample Email" %} +**Assignment Date:** February 17, 2018 + +**Assignment:** summarize Aatrix Software, Inc. v. Green Shades Software, Inc., No. 2017-1452, 2018 WL 843288 \(Fed. Cir. Feb. 14, 2018\) along with links to at least two outside sources. You can find examples of posts at [https://jolt.law.harvard.edu/digest/category/?cat=patent](https://jolt.law.harvard.edu/digest/category/?cat=patent). + +**Draft Deadline** \(Contributor send draft to me and Editor\): 11:59 pm on Thursday, Feb 21. + +**Edits Deadline** \(Editor send marked up draft to me and Contributor\): noon on Sat, Feb 24. + +Thanks for writing for Digest this semester! According to the Fall 2017 Report Schedule, <**Contributor**>, you have been assigned the role of Digest Contributor for this week. **<Editor>**, you are assigned the role or Report Editor. + +**ASSIGNMENT** +<**Contributor>**, your task is to summarize Aatrix Software, Inc. v. Green Shades Software, Inc., No. 2017-1452, 2018 WL 843288 \(Fed. Cir. Feb. 14, 2018\). + +At issue here is whether the patented technology should have been patent-eligible. 35 U.S.C. § 101 defines what may be patented. Courts have consistently held that abstract ideas, laws of nature, and natural phenonmenons are not patentable. The question then often turns on what falls in each of these three categories. Though commonplace, the issue is probably the most fundamental question in patent law and supported by one of the least defined doctrines in the field. + +You will almost certainly come across the Alice test. Courts applying the test engage in a two-step inquiry. In step one, courts figure out whether the matter at issue falls in one of the three patent-ineligible categories: abstract idea, laws of nature, or natural phenomenon. If not, then it is patentable. If so, then the courts ask whether there is an "inventive concept" that "transforms" the patent-ineligible matter into something "more" that is patentable. Readers will be most curious about the facts the courts considered in reaching their decisions on each of these steps. + +**<Editor>**, your job is to ensure the report is substantively accurate and give suggestions on big picture flow. Defer to the Contributor on writing style. + +This can be a very confusing case so don't hesitate to email me with any questions. +You'll find the case at [http://www.cafc.uscourts.gov/sites/default/files/opinions-orders/17-1452.Opinion.2-12-2018.1.PDF](http://www.cafc.uscourts.gov/sites/default/files/opinions-orders/17-1452.Opinion.2-12-2018.1.PDF) \(also attached\). You can find other Federal Circuit cases at [http://www.cafc.uscourts.gov/opinions-orders/search/report.html](http://www.cafc.uscourts.gov/opinions-orders/search/report.html). + +In addition to summarizing the case, your article should also include at least 2 hyperlinks to related material and/or commentary. These can include briefs \(filed by the party or amicus\), legal blogs, JOLT articles or Digest posts, news articles. + +You can find an example of a Digests post [here](http://jolt.law.harvard.edu/digest/two-way-media-v-comcast). + +You should follow the appropriate Digest Report guides: [Style & Citations Guide](reportstylecitation.md), [Contributor's Guide](reportcontributorguide.md), and [Editor's Guide](reporteditorguide.md). On occasion, the Style Guide requires you to follow the Bluebook \(though we never pincite\). JOLT maintains several online bluebook accounts to help with that process. Log-in with the following credentials at [www.legalbluebook.com](http://www.legalbluebook.com/). + +Accounts: \[excluded\] + +Password: \[excluded\] + +**<Contributor>**, please send **<Editor>** and me your draft by 11:59pm Wed, Feb 21. **<Editor>**, please send the marked up draft to **<Contributor>** and me by 11:59pm Sat, Feb 24. Requirements are listed in your corresponding guides. Please follow them closely. + +Lastly, Digest is looking to constantly improve the publication process. If you find any part of it confusion -- the requirements, guides, communication, etc. -- please let us know so that we can make adjustments. +{% endtab %} +{% endtabs %} + +{% hint style="success" %} +#### Your Responsibilities + +After receiving your assignment from the Subject Matter Coordinator \(SMC\), immediately "reply all" to the email and: + +1. Confirm to the SMC and Contributor that you have received and can complete the assignment. +2. Alert the SMC and Contributor to any problems that may delay your submission +{% endhint %} ## Step 3: Editing -As an Report Editor, you will work with the Contributor to ensure the report is publication-ready. You should make sure that the Contributor's piece follows the [Style & Citations Guide](reportstylecitation.md) and comply with the recommendations laid out in [Step 3 of the Contributor's Guide](reportcontributorguide.md#step3). +{% hint style="success" %} +**Your Responsibilities** -Enter your edits directly into the Google Docs in ["Suggest Edits" mode](https://support.google.com/docs/answer/6033474?co=GENIE.Platform%3DDesktop&hl=en). +As an Report Editor, you will work with the Contributor to ensure the report is publication-ready. + +1. Read the primary source and links provided by the SMC to check for **substantive accuracy** +2. Ensure the tone of the piece is **impartial** and any opinions are attributed to a source. [Step 3 of the Contributor's Guide](https://jolt.gitbook.io/jolt-digest-citation-and-style-guide/reports/reportcontributorguide#step3) may be helpful to understand how a piece should be structured. +3. Make sure that the Contributor's piece follows the [Style & Citations Guide](reportstylecitation.md) +4. Copyedit the piece for typos and grammatical errors +{% endhint %} + +The Contributor will have shared in the assigning email thread the link to the Google Doc containing the draft \(see [Step 4 of the Contributor's Guide](reportcontributorguide.md#step4) for more details\). Enter your comments and edits directly into the Google Docs in ["Suggest Edits" mode](https://support.google.com/docs/answer/6033474?co=GENIE.Platform%3DDesktop&hl=en). ## Step 4: Moving the Report Forward -The Contributor will have shared in the assigning email thread the link to the Google Doc containing the draft \(see [Step 4 of the Contributor's Guide](reportcontributorguide.md#step4) for more details\). Make your comments and suggestions directly within the Google Doc. Once you're done with your comments and suggestions, reply all in the assigning email threads letting everyone know \(1\) a summary of your edits; and \(2\) any questions/concerns that arose during editing. +{% hint style="success" %} +**Your Responsibilities** + +Notify your Contributor when you are done with edits, and be available to look over any changes made. +{% endhint %} + +Once you're done with your comments and suggestions, reply all in the assigning email threads letting everyone know \(1\) a summary of your edits; and \(2\) any questions/concerns that arose during editing. + +Then Contributor then has at least 24 hours to implement your suggestions. This time period is meant to allow a back and forth between you and the Contributor to refine your piece before the SMC reviews it. The SMC may offer an additional round of edits. You and the Editor will be asked to review the Report one last time before it is published. + +## Step 5: Feedback + +{% hint style="warning" %} +**You must fill out the feedback form to receive feedback.** +{% endhint %} + +After the Report is published online, you will get an email from the Digest Reports Editor with a link and a feedback form. We ask for your feedback on: + +1. Your experience editing the Report \(to help us improve the process\) +2. Your experience working with the SMC and Contributor \(to help us make promotion decisions\) + +We also provide the opportunity to give **anonymous** feedback to your Contributor. The Digest Reports Editor will combine their feedback with your feedback and the SMC's. The feedback you receive will be similarly anonymized. ## Thank you! From b6fb7274f538b43a158aa37d411a991c70a7eb76 Mon Sep 17 00:00:00 2001 From: Alicia Loh Date: Sat, 14 Sep 2019 03:44:38 +0000 Subject: [PATCH 07/11] GitBook: [2.0.0] 2 pages modified --- reports/reportcontributorguide.md | 2 +- reports/reporteditorguide.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md index 2695151..ea4b65a 100644 --- a/reports/reportcontributorguide.md +++ b/reports/reportcontributorguide.md @@ -25,7 +25,7 @@ You, the Digest Contributor, will be assigned reports according to the availabil Here's what the editing timeline will look like \(unless otherwise stated\): * **Sunday Night**: ****SMC will send the assigning email -* **Thursday by 11:59pm**: ****Contributor finishes draft report +* **Thursday by noon**: ****Contributor finishes draft report * **Saturday by noon**: ****Editor submits all edits * **Sunday by noon**: Contributor finalizes changes * **Monday**: SMC and Digest Reports Editor makes final edits, and Report is published diff --git a/reports/reporteditorguide.md b/reports/reporteditorguide.md index 114e9a7..ae6d504 100644 --- a/reports/reporteditorguide.md +++ b/reports/reporteditorguide.md @@ -23,7 +23,7 @@ You, the Report Editor, are tasked with reviewing the Contributor's draft for su Here's what the editing timeline will look like \(unless otherwise stated\): * **Sunday Night**: ****SMC will send the assigning email -* **Thursday by 11:59pm**: ****Contributor finishes draft report +* **Thursday by noon**: ****Contributor finishes draft report * **Saturday by noon**: ****Editor submits all edits * **Sunday by noon**: Contributor finalizes changes * **Monday**: SMC and Digest Reports Editor makes final edits, and Report is published From e00e9fe0ce80b5e7ee2155c490402f92ff9b8a60 Mon Sep 17 00:00:00 2001 From: Alicia Loh Date: Mon, 16 Sep 2019 00:16:53 +0000 Subject: [PATCH 08/11] GitBook: [2.0.0] 4 pages modified --- README.md | 2 +- notes/notecontributorguide.md | 15 ++++++++++----- reports/reportcontributorguide.md | 8 ++++---- reports/reporteditorguide.md | 14 ++++++++------ 4 files changed, 23 insertions(+), 16 deletions(-) diff --git a/README.md b/README.md index ef32d55..e2168bf 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,7 @@ Digest features short articles on new, precedential, or interesting cases; new l **Digest Executive Editor** \(Mindy Nam\) supervises the entire Digest team, creates the Digest publication schedule, and provides an additional layer of editing for all publications. -**Digest Reports Editor** \(Alicia Loh\) oversees all Digest Reports: assisting the SMCs to generate topics and schedule assignments, coordinating the assignment process, and providing a final layer of editing. +**Digest Engagement Editor** \(Alicia Loh\) oversees all Digest Reports: assisting the SMCs to generate topics and schedule assignments, coordinating the assignment process, and providing a final layer of editing. **Subject Matter Coordinators \(SMCs\)** \(Sam Santopaolo, Justin Fishman, and Andrew Distell\) assign topics to and work closely with Contributors and Report Editors on their subject matter teams to publish Digest Reports. diff --git a/notes/notecontributorguide.md b/notes/notecontributorguide.md index 4659c9c..f7cd6fd 100644 --- a/notes/notecontributorguide.md +++ b/notes/notecontributorguide.md @@ -2,13 +2,18 @@ ## Welcome to the Note Contributor's Guide! -A _Digest_ Note proffers a **novel analysis** on an issue related to law and technology. It contributes something new and interesting to the field. While a Note may include economic, cultural, or other types of arguments, it must revolve around the law. +A Digest Note proffers a **novel analysis** on an issue related to law and technology. It contributes something new and interesting to the field. While a Note may include economic, cultural, or other types of arguments, it must revolve around the law. You should make sure that your Note idea is not preempted; do some background research and work with your Note Editor on refining the idea. -**Your Tasks** 1. Come up with a **novel analysis** related to law and technology. 2. Provide an outline. 3. Write a 1500-2000 word analysis piece on the topic. +{% hint style="success" %} +**Your Tasks** -1. Respond to suggestions from the [Note Editor](noteeditorguide.md). +1. Come up with a **novel analysis** related to law and technology. +2. Provide an outline. +3. Write a 1500-2000 word analysis piece on the topic. +4. Respond to suggestions from the [Note Editor](noteeditorguide.md). +{% endhint %} ## Requirements @@ -28,13 +33,13 @@ Possible topics include ### Length -Your Note should be within 1500-2000 words. You may go over 2000 words but only if both you and your Note Editor agree that your thesis requries the extra space. Every Note will have an objective portion, that sets up the context of your piece, and a subjective portion, that lays out your argument. There is no required distribution of words between the two portions -- the only requirement is that there is a subjective portion. +Your Note should be within 1500-2000 words. You may go over 2000 words, but only if both you and your Note Editor agree that your thesis requries the extra space. Every Note will have an objective portion, that sets up the context of your piece, and a subjective portion, that lays out your argument. There is no required distribution of words between the two portions — the only requirement is that there is a subjective portion. Citations will not count towards the word limit. ### Citations -Notes are more formal pieces than [_Digest_ Reports](../reports/reportcontributorguide.md). And so, you will need to provide pincites for every statement you attribute to someone else. **Follow the Bluebook whitepages subject to the rules laid out in the** [**Notes Style and Citation Guide**](notestylecitation/)**.** When submitting drafts, provide citations in endnotes rather than footnotes. +Notes are more formal pieces than [Digest Reports](../reports/reportcontributorguide.md). And so, you will need to provide pincites for every statement you attribute to someone else. **Follow the Bluebook whitepages subject to the rules laid out in the** [**Notes Style and Citation Guide**](notestylecitation/)**.** When submitting drafts, provide citations in endnotes rather than footnotes. ## Logistics diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md index ea4b65a..e60440d 100644 --- a/reports/reportcontributorguide.md +++ b/reports/reportcontributorguide.md @@ -28,7 +28,7 @@ Here's what the editing timeline will look like \(unless otherwise stated\): * **Thursday by noon**: ****Contributor finishes draft report * **Saturday by noon**: ****Editor submits all edits * **Sunday by noon**: Contributor finalizes changes -* **Monday**: SMC and Digest Reports Editor makes final edits, and Report is published +* **Monday**: SMC and Digest Engagement Editor makes final edits, and Report is published ## Step 2: Receiving and Confirming Receipt of Your Assignment @@ -46,7 +46,7 @@ The SMC will send you and the Report Editor an assigning email with: 4. Link to [Contributor](reportcontributorguide.md#welcome-to-the-report-contributors-guide), [Editor](reporteditorguide.md#welcome-to-the-report-editors-guide), and [Style & Citation Guides](reportstylecitation.md) 5. Credentials for online Bluebook access -If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Reports Editor, who is also available to answer questions. +If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Engagement Editor, who is also available to answer questions. {% endtab %} {% tab title="Sample Email" %} @@ -230,12 +230,12 @@ The easiest way to do this is to share a link in the assigning email thread. The **You must fill out the feedback form to receive substantive feedback on your writing.** {% endhint %} -After the Report is published online, you will get an email from the Digest Reports Editor with a link and a feedback form. We ask for your feedback on: +After the Report is published online, you will get an email from the Digest Engagement Editor with a link and a feedback form. We ask for your feedback on: 1. Your experience writing the Report \(to help us improve the process\) 2. Your experience working with the SMC and Editor \(to help us make promotion decisions\) -We also provide the opportunity to give **anonymous** feedback to your Editor. The Digest Reports Editor will combine their feedback with your feedback and the SMC's. The feedback you receive will be similarly anonymized. +We also provide the opportunity to give **anonymous** feedback to your Editor. The Digest Engagement Editor will combine their feedback with your feedback and the SMC's. The feedback you receive will be similarly anonymized. ## Thank you! diff --git a/reports/reporteditorguide.md b/reports/reporteditorguide.md index ae6d504..549ccf7 100644 --- a/reports/reporteditorguide.md +++ b/reports/reporteditorguide.md @@ -18,7 +18,7 @@ Subject Matter Coordinators \(SMCs\) are constantly looking for “hot” law & ## Step 1: Getting Started -You, the Report Editor, are tasked with reviewing the Contributor's draft for substantive and technical accuracy. You will usually have about two days after the Contributor has shared the first draft to give comments and suggestions. You'll be working with the Contributor in finalizing the draft before handing it off to the SMC and Digest Reports Editor \(Alicia Loh\) for a final review and publication. +You, the Report Editor, are tasked with reviewing the Contributor's draft for substantive and technical accuracy. You will usually have about two days after the Contributor has shared the first draft to give comments and suggestions. You'll be working with the Contributor in finalizing the draft before handing it off to the SMC and Digest Engagement Editor \(Alicia Loh\) for a final review and publication. Here's what the editing timeline will look like \(unless otherwise stated\): @@ -26,7 +26,7 @@ Here's what the editing timeline will look like \(unless otherwise stated\): * **Thursday by noon**: ****Contributor finishes draft report * **Saturday by noon**: ****Editor submits all edits * **Sunday by noon**: Contributor finalizes changes -* **Monday**: SMC and Digest Reports Editor makes final edits, and Report is published +* **Monday**: SMC and Digest Engagement Editor makes final edits, and Report is published ## Step 2: Receiving and Confirming Receipt of Your Assignment @@ -44,7 +44,7 @@ The SMC will send you and the Contributor an assigning email with: 4. Link to [Contributor](reportcontributorguide.md#welcome-to-the-report-contributors-guide), [Editor](reporteditorguide.md#welcome-to-the-report-editors-guide), and [Style & Citation Guides](reportstylecitation.md) 5. Credentials for online Bluebook access -If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Reports Editor, who is also available to answer questions. +If the email is missing any information OR you have questions: immediately contact your Subject Matter Coordinator. If the Coordinator does not respond, feel free to contact the Digest Engagement Editor, who is also available to answer questions. {% endtab %} {% tab title="Sample Email" %} @@ -128,14 +128,16 @@ Then Contributor then has at least 24 hours to implement your suggestions. This **You must fill out the feedback form to receive feedback.** {% endhint %} -After the Report is published online, you will get an email from the Digest Reports Editor with a link and a feedback form. We ask for your feedback on: +After the Report is published online, you will get an email from the Digest Engagement Editor with a link and a feedback form. We ask for your feedback on: 1. Your experience editing the Report \(to help us improve the process\) 2. Your experience working with the SMC and Contributor \(to help us make promotion decisions\) -We also provide the opportunity to give **anonymous** feedback to your Contributor. The Digest Reports Editor will combine their feedback with your feedback and the SMC's. The feedback you receive will be similarly anonymized. +We also provide the opportunity to give **anonymous** feedback to your Contributor. The Digest Engagement Editor will combine their feedback with your feedback and the SMC's. The feedback you receive will be similarly anonymized. ## Thank you! -The JOLT Digest team thanks you for your time and energy. Please feel free to email the [_Digest Masthead_](https://jolt.law.harvard.edu/masthead) if you have any concerns or suggestions on improving the process! +The JOLT Digest team thanks you for the time you will be putting into creating Digest content. We hope you enjoy the content creation process and working with the subject matter of your assignments. + +Follow the JOLT [Twitter](https://www.twitter.com/harvardjolt) or [Facebook Page](https://www.facebook.com/harvardjolt) to stay up to date on all Digest publications! From e02207bae23d4176353cec61f6d91b07d86af0e6 Mon Sep 17 00:00:00 2001 From: Alicia Loh Date: Mon, 4 Nov 2019 13:18:01 +0000 Subject: [PATCH 09/11] GitBook: [2.0.0] 2 pages modified --- README.md | 8 ++++---- reports/reportstylecitation.md | 8 +++++++- 2 files changed, 11 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index e2168bf..9bba9c2 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ Digest features short articles on new, precedential, or interesting cases; new l ## Meet the team! -**Digest Executive Editor** \(Mindy Nam\) supervises the entire Digest team, creates the Digest publication schedule, and provides an additional layer of editing for all publications. +**Digest Executive Editor** \(Mindy Nam\) supervises the entire Digest team, which is comprised of the Digest Reports program, the Federal Circuit Panel program, the Digest Notes and Comments, and the JOLT Digest Podcast. She also creates the Digest publication schedule, and provides an additional layer of editing for all publications. **Digest Engagement Editor** \(Alicia Loh\) oversees all Digest Reports: assisting the SMCs to generate topics and schedule assignments, coordinating the assignment process, and providing a final layer of editing. @@ -18,13 +18,13 @@ Digest features short articles on new, precedential, or interesting cases; new l **Digest Content Editors** \(Or-el Vaknin and Anita Liu\) take the lead on seeing Digest Student Notes and Comments from submission to publication. This involves back-and-forth on substantive edits with the authors to make sure their pieces meet Digest standards. -**Digest Development Manager** \(Alexandra Mushka\) reaches out to professors, practitioners, and non-HLS law students to grow the JOLT Digest community. +**Digest Development Manager** \(Alexandra Mushka\) reaches out to professors, practitioners, academic institutions, and non-HLS law students to grow the JOLT Digest community. **Federal Circuit Panel Writers** \(Hye Yoon Hwang, Meera Midha, Kaye Horstman, and Will Czaplyski\) write Notes on current issues in the Federal Circuit. -**Podcast Content Team** \(Flora Wang, Minnie Che, Nick Berk, and Oladeji Tiamiyu\) leads the creation of podcast episodes and researches the subject material. +**Podcast Content Team** \(Flora Wang, Minnie Che, Nick Berk, and Coco Zhang\) leads the creation of podcast episodes and researches the subject material. -**Podcast Production Team** \(Nick Curry and Bowen Wang\) record and edit each episode. +**Podcast Production Team** \(Nick Curry and Bowen Wang\) manage recording logistics and finalize the production of each episode. \*\*\*\* diff --git a/reports/reportstylecitation.md b/reports/reportstylecitation.md index 9d62601..b3b5da7 100644 --- a/reports/reportstylecitation.md +++ b/reports/reportstylecitation.md @@ -29,6 +29,12 @@ When listing three or more things, separate each pair with a comma, including th > **Example:** Lions, tigers, and bears. +## Capitalization + +Only capitalize "court" when referencing the US Supreme Court or the full name of the court. + +> **Example:** "The District Court for the Northern District of California ****held..." or "The court held..." + ## Symbols Outside of citations, do not use "§" and "¶." Instead, spell out and capitalize "Section" and "Paragraphs" in place of symbols. @@ -46,7 +52,7 @@ Despite the Digest’s more informal style, we strive to maintain the high stand Documents that are the focus of an article, such as a slip opinion, statute, letter, etc., should be properly Bluebooked and located at the beginning of the article. Pincites need not be included throughout the article. > **DOJ v. BMI: DOJ Argues BMI’s Fractional Licensing Practice Violates Consent Decree** -> By \[author\] -- Edited by \[editor\] +> By \[author\] - Edited by \[editor\] > Brief of Appellant, United States v. Broadcast Music, Inc., No. 16-3830-cv \(2d. Cir. May 18, 2017\), [brief](http://www.djcounsel.com/wp-content/uploads/2017/05/2017-DOJ-Brief-BMI-Full-Work-Licensing.pdf) hosted by DJ Counsel. > > ... body ... From d877e0e4f2274fb1158ea41c6c7199070230a574 Mon Sep 17 00:00:00 2001 From: Alicia Loh Date: Wed, 29 Jan 2020 21:13:26 +0000 Subject: [PATCH 10/11] GitBook: [2.0.0] 3 pages modified --- README.md | 4 +--- reports/reportcontributorguide.md | 6 ++++-- reports/reporteditorguide.md | 6 +++--- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 9bba9c2..db37d36 100644 --- a/README.md +++ b/README.md @@ -16,9 +16,7 @@ Digest features short articles on new, precedential, or interesting cases; new l **Report Contributors** and **Editors** work together to publish Digest Reports that provide overviews on important new developments in law and technology. -**Digest Content Editors** \(Or-el Vaknin and Anita Liu\) take the lead on seeing Digest Student Notes and Comments from submission to publication. This involves back-and-forth on substantive edits with the authors to make sure their pieces meet Digest standards. - -**Digest Development Manager** \(Alexandra Mushka\) reaches out to professors, practitioners, academic institutions, and non-HLS law students to grow the JOLT Digest community. +**Digest Content Editors** \(Or-el Vaknin and Anita Liu\) take the lead on seeing Digest Student Notes and Comments from submission to publication. This involves back-and-forth on substantive edits with the authors to make sure their pieces meet Digest standards. **Federal Circuit Panel Writers** \(Hye Yoon Hwang, Meera Midha, Kaye Horstman, and Will Czaplyski\) write Notes on current issues in the Federal Circuit. diff --git a/reports/reportcontributorguide.md b/reports/reportcontributorguide.md index e60440d..c1312a7 100644 --- a/reports/reportcontributorguide.md +++ b/reports/reportcontributorguide.md @@ -28,7 +28,7 @@ Here's what the editing timeline will look like \(unless otherwise stated\): * **Thursday by noon**: ****Contributor finishes draft report * **Saturday by noon**: ****Editor submits all edits * **Sunday by noon**: Contributor finalizes changes -* **Monday**: SMC and Digest Engagement Editor makes final edits, and Report is published +* **The following week**: SMC and Digest Engagement Editor makes final edits, and Report is published ## Step 2: Receiving and Confirming Receipt of Your Assignment @@ -122,7 +122,7 @@ The purpose of Digest Reports is to provide a relatively brief and ideologically 1. Read the original source provided in the assignment email 2. Draft an impartial summary of the assignment email -3. Include in the summary **two** links to outside sources +3. Include in the report at least **two** links to outside sources {% endhint %} {% tabs %} @@ -159,6 +159,7 @@ Please ensure that each submission adheres to the general organizational format 1. Commentary: news articles, if accurate, & scholarly comment 2. Related materials 7. Optional: one line describing yourself and your interests which will be included at the end of your contributor post. e.g. "\[Contributor’s name\] is a \(1L, 2L, 3L\) at the Harvard Law School." +8. **Social Media Tagline**: Your post will be tweeted out when published. Please write a tweet for us to use. Include hashtags as appropriate, and please remember Twitter has a 280 character limit. Examples can be found at the [JOLT Twitter](https://www.twitter.com/HarvardJOLT) account. Feel free to include your username for us to tag you with. {% endtab %} {% tab title="Sample Case Report" %} @@ -220,6 +221,7 @@ Please share your draft on Google Doc with the following: * Report Editor * Assigning Subject Matter Coordinator +* Digest Engagement Editor \(aloh@jd20\) * Digest Account \(joltdigest@mail.law.harvard.edu\) The easiest way to do this is to share a link in the assigning email thread. The Editor will have about three days to add comments and suggestions in the Google Doc. Please review them, finalize the draft, and notify the assigning SMC \(via the email thread\). The SMC will take another look and may offer an additional round of edits. You and the Editor will be asked to review the Report one last time before it is published. diff --git a/reports/reporteditorguide.md b/reports/reporteditorguide.md index 549ccf7..24ae24e 100644 --- a/reports/reporteditorguide.md +++ b/reports/reporteditorguide.md @@ -26,7 +26,7 @@ Here's what the editing timeline will look like \(unless otherwise stated\): * **Thursday by noon**: ****Contributor finishes draft report * **Saturday by noon**: ****Editor submits all edits * **Sunday by noon**: Contributor finalizes changes -* **Monday**: SMC and Digest Engagement Editor makes final edits, and Report is published +* **The following week**: SMC and Digest Engagement Editor makes final edits, and Report is published ## Step 2: Receiving and Confirming Receipt of Your Assignment @@ -105,7 +105,7 @@ As an Report Editor, you will work with the Contributor to ensure the report is 1. Read the primary source and links provided by the SMC to check for **substantive accuracy** 2. Ensure the tone of the piece is **impartial** and any opinions are attributed to a source. [Step 3 of the Contributor's Guide](https://jolt.gitbook.io/jolt-digest-citation-and-style-guide/reports/reportcontributorguide#step3) may be helpful to understand how a piece should be structured. 3. Make sure that the Contributor's piece follows the [Style & Citations Guide](reportstylecitation.md) -4. Copyedit the piece for typos and grammatical errors +4. Copy edit the piece for typos and grammatical errors {% endhint %} The Contributor will have shared in the assigning email thread the link to the Google Doc containing the draft \(see [Step 4 of the Contributor's Guide](reportcontributorguide.md#step4) for more details\). Enter your comments and edits directly into the Google Docs in ["Suggest Edits" mode](https://support.google.com/docs/answer/6033474?co=GENIE.Platform%3DDesktop&hl=en). @@ -118,7 +118,7 @@ The Contributor will have shared in the assigning email thread the link to the G Notify your Contributor when you are done with edits, and be available to look over any changes made. {% endhint %} -Once you're done with your comments and suggestions, reply all in the assigning email threads letting everyone know \(1\) a summary of your edits; and \(2\) any questions/concerns that arose during editing. +Once you're done with your comments and suggestions, reply all in the assigning email thread letting everyone know \(1\) a summary of your edits; and \(2\) any questions/concerns that arose during editing. Then Contributor then has at least 24 hours to implement your suggestions. This time period is meant to allow a back and forth between you and the Contributor to refine your piece before the SMC reviews it. The SMC may offer an additional round of edits. You and the Editor will be asked to review the Report one last time before it is published. From 6c1a0fcd5665882517d0a8771672adaa852098fb Mon Sep 17 00:00:00 2001 From: Alicia Loh Date: Mon, 9 Mar 2020 20:00:38 +0000 Subject: [PATCH 11/11] GitBook: [2.0.0] one page modified --- reports/reportstylecitation.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/reports/reportstylecitation.md b/reports/reportstylecitation.md index b3b5da7..ab74a9f 100644 --- a/reports/reportstylecitation.md +++ b/reports/reportstylecitation.md @@ -124,10 +124,10 @@ Where case names are included in endnotes, follow case name abbreviations in Tab If a PDF of a court document is available through an open access online source \(i.e., not through Westlaw or Lexis Nexis\), hyperlink to the source from the document type or, if none, case name in the Bluebook citation. If the PDF is hosted by a non-court source, include “hosted by” language with the hyperlink on the document type \(not a Bluebook abbreviation\). -> **Example:** [MGA Entertainment, Inc. v. Mattel, Inc.](http://www.sunsteinlaw.com/media/BratzTCC.pdf), No. 09-55673 \(9th Cir. July 22, 2010\), hosted by sunsteinlaw.com. -> **Example:** Viacom International Inc. v. YouTube, Inc., No. 07 Civ. 2103 \(S.D.N.Y. June 23, 2010\), [slip opinion](http://docfiles.justia.com/cases/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf), hosted by Justia.com. -> **Example:** Complaint for Declaratory Judgment and Injunctive Relief, GoldieBlox, Inc. v. Island Def Jam Music Group, A Div. of UMG Recordings, Inc., No. 3:13-cv-05428 \(N.D. Cal. Nov. 21, 2013\), [complaint](http://www.scribd.com/doc/186402972/Beastie) hosted by Scribd. -> **Not:** Viacom Int’l Inc. v. YouTube, Inc., No. 07 Civ. 2103 \(S.D.N.Y. June 23, 2010\), [slip op.](https://cases.justia.com/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf) hosted by Justia.com +> **Example:** [MGA Entertainment, Inc. v. Mattel, Inc.](http://www.sunsteinlaw.com/media/BratzTCC.pdf) \(9th Cir. July 22, 2010\)\(No. 09-55673\), hosted by sunsteinlaw.com. +> **Example:** Viacom International Inc. v. YouTube, Inc. \(S.D.N.Y. June 23, 2010\)\(No. 07 Civ. 2103\), [slip opinion](http://docfiles.justia.com/cases/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf), hosted by Justia.com. +> **Example:** Complaint for Declaratory Judgment and Injunctive Relief, GoldieBlox, Inc. v. Island Def Jam Music Group, A Div. of UMG Recordings, Inc. \(N.D. Cal. Nov. 21, 2013\)\(No. 3:13-cv-05428\), [complaint](http://www.scribd.com/doc/186402972/Beastie) hosted by Scribd. +> **Not:** Viacom Int’l Inc. v. YouTube, Inc. \(S.D.N.Y. June 23, 2010\)\(No. 07 Civ. 2103\), [slip op.](https://cases.justia.com/federal/district-courts/new-york/nysdce/1:2007cv02103/302164/364/0.pdf) hosted by Justia.com. ## Substance