Git Product home page Git Product logo

termination-of-transfer's People

Contributors

aamike avatar dependabot[bot] avatar hugosolar avatar kgodey avatar mattl avatar peterspdx avatar timidrobot avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

termination-of-transfer's Issues

Revised 2.d.i

Changed a fail to a flag on the basis of legal review (pre-78 creation should no longer fail)

Additionally, added flag to "don't know" answer to post-78.

See proposed decision tree for details.

New glossary entries needed

This might be a good project for clinical assistance. I'll edit this post, adding needed entries as they arise.

  1. Copyright Notice
  2. Copyright Registration
  3. Special order or commission (currently links to work for hire entry)

Failing after 1.f.i in the 1950s

James Grimmelmann had two very similar cases resulting in failure at this point:

The first:

Also loops back to the start. I haven’t been able to get to the details of the work on any set of inputs; it either freezes or restarts no matter what I enter.

When was the work created? 1950
Has the work been published? yes
When was the work first published? 1950
Works from 1989 and earlier usually display a copyright notice. Did the work have a copyright notice? yes
Has the work been registered with the United State Copyright Office? yes
When was the work registered with the United States Copyright Office? (Leave blank if unknown) 1950
What is the date of the agreement or transfer?
If the agreement predates the work’s creation, please enter the creation year.

The second:

When was the work created? 1950
Has the work been published? yes
When was the work first published? 1951
Works from 1989 and earlier usually display a copyright notice. Did the work have a copyright notice? yes
Has the work been registered with the United State Copyright Office? yes
When was the work registered with the United States Copyright Office? (Leave blank if unknown) 1951

I'm playing around trying to isolate what's wrong, because similar entries work fine for different years (e.g., clustered around 1928 or 1960)

Availability analysis in output

Present output (both blurb and PDF) doesn't go through the availability logic.

That is, a termination right —

  • may have existed and expired
  • may presently exist
  • may not yet exist, but be expected in the future

This is the " [[is presently/was/will be]]" language in conclusion key A. Should use the tense appropriate given the relationship between the present time and the termination window.

Problem example pictured below (in the case of a future right)
Related issue to be created regarding output of window information.

screen shot 2016-08-15 at 7 05 55 pm

Make question 3.e optional

On advice of counsel, let's not force an answer that makes the result overly specific to a given case.

Create inventory of all pages on website and wiki relating to tool

We have the main pages, but need to come up with a complete inventory of the pages that are linked to from the tool that provide additional info about legal concepts and similar in preparation for our legal review and transfer of pages and content to Authors Alliance.

UX Issues

  • Ability to step backwards after the tool completes is a must (currently, users must start over)
  • Do not frontload metadata entry (it's only relevant if tools completes as a positive)
  • Frontload date questions — the present approach is duplicative (it asks both regarding work for hire and regarding general eligibility)
  • Don't automatically redirect to the PDF on completion—generate a link to it instead.

Fix frozen screen and next/back functionality for this search

The screen froze with this search:

When was the work created? 1992
Has the work been published? yes
When was the work first published? 1993
Has the work been registered with the United State Copyright Office? no
What is the date of the agreement or transfer?
If the agreement predates the work’s creation, please enter the creation year. 1995
Did the agreement or transfer include the right of publication? yes

After providing a summary of the answers, at this point: “Both notice window and copyright status look good, let’s get some more details!”, both the “back” and “Next” buttons did not seem to function at all. (Note that the searcher purposefully had the transfer date be after the publication date — just to see what the tool would do with that type of situation).
.

"Conclusion" doesn't reflect result

The flag looks looks good here, and the windows look good, but it says up top that notification is possible—contradicting the flag that says we're outside the notice window.

We could just scrap the big bold conclusion, but that text is duplicated on the questionnaire page so it would be best to have it reflect the circumstances if possible.

Text edits to PDF output form - IMPT needed before demo recording on Friday

  1. Under Termination of Transfer Information Sheet at top, should read:
    Creative Commons and Authors Alliance
  2. Just under that, in bold and italicized (can be smaller text), move up from the first paragraph under the division line:
    This is a beta information sheet produced for testing purposes only.
  3. Under the top line, revise first sentence to read as follows: This is an information sheet generated by the Termination of Transfer Tool currently being developed by Creative Commons and Authors Alliance.
  4. Change the link to the FAQ at the top from the old beta to the new beta that is hosted at: http://labs.creativecommons.org/demos/termination-of-transfer/

FAQ Issues

  • Include a discrete list of all possible outcomes

Code audit

Checking code base against annotated decision tree 0.1

Due May 17

Information provided in PDF output

Let's be sure to include at least the:
• notice window (beginning and end)
• termination window (beginning and end)
(these are the most important things)

But I think it would be also good to have (if applicable):
• the publication date
• the registration date
• the creation date

Display of dual window scenarios not working

We have two scenarios where there might be two possible termination windows:

Under § 304 we can have the normal termination or the $d_term.

Under § 203, if we don't know whether publication rights were transferred, the term can be a regular term or a $p_term.

Presently, neither $d_terms (and their notice periods) nor $p_terms (and their notices periods) seem to be generating int he PDF output.

Flags Are Not Cleared When Back Button Is Pressed

If the user selects the "Back" button, changes the information they have input, then goes forward they may change the flags that should be applied. But we do not remove flags as we go back. This may lead to incorrect flags in the input.

Change the back button behaviour to strip specified flags, or simply remove the back button if this would be too complex in the available time (if we would have to reference count flags for example).

Not seeing all flags

screen shot 2016-09-21 at 12 49 29 pm

screen shot 2016-09-21 at 12 53 04 pm

The inputs above should also trigger flags:
B.1 (triggered at stage 1.a.i.1.b of the decision tree) (no copyright notice)
C.1 (triggered at stage 2.e.i of the decision tree) (possible renegotiations)

(these flags also do not appear when the engine is run solely to trigger them individually)

Revisions to public domain determinations and flags

In the proposed decision tree. Two changes:

First: step 1.e (§ 304 analysis) — added test / flag for possible expiration (If $cright_year < 1950 : flag B.iv (Possible expired copyright—possibly public domain);)

Next: copyright term expiration (post-78 works + § 303 works only — i.e., "life of the author" terms) — added test as new 2.b.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.