See openfisca/openfisca-france#375

Add a “Improve this website” link in the footer to foster collaboration.

As a product manager,
I can track pageviews on the legislation explorer,
To follow the efficiency of the search feature

The attribut "Formules utilisant ce paramètre" is always missing.

Example

As a user trying to access an obsolete variable,
I get information about the fact that it could have been removed and what to do about it,
So that I don't believe there is an error with the software

• Link “En savoir plus” main link to doc.openfisca.fr.

For variables:

• Link Entity types to Entities documentation page.
• Link periods to Periods documentation page.
• Link Variable to Variables documentation page.

As a user,
I can know which version of the source legislation is used to present the variables,
So that I don't waste time looking at obsolete information

In https://legislation.openfisca.fr/variables the node aefa.py is empty.

This should be because https://github.com/openfisca/openfisca-france/blob/master/openfisca_france/model/prestations/minima_sociaux/aefa.py contains only a dated variable.

Right now they have been deactivated

UI needs to be discussed.

Propositions :

• Select field to choose the date (with all the dates where the law has changed)
• Slider to choose the date
• Date picker
• All values displayed in collapsable blocks
• A graphical plot

(Try to) implement an "open in editor" link with custom protocol (edit://) like JOSM.

See https://legislation.openfisca.fr/parameters/ir.bareme

Go to "Historique exhaustif par tranche" then look at "taux", it is "€" but should be "%".

As user I want to look for a variable and I do not want to be distracted by the parameter (and vice-versa).
I should be able to restrict my search accordingly.

Look for CSG on the parameters page and you will see what I mean. (Might be related to openfisca/openfisca-core#436).

Run npm run lint and npm run build on CircleCI.

The current ordering is only alphabetical.

There should be a sorting algorithm that priories matches according to the position of the match in the variable name (the earlier the better).

When clicking on on Formules utilisant cette variable or Variables utilisées, the code source is nbot updated

As a Producer,
I don't have to choose between searching within variables and parameters.

On https://legislation.openfisca.fr/impot_revenu.autre.finpfl

The API returns a boolean: https://api-test.openfisca.fr/parameter/impot_revenu.autre.finpfl

But this condition uses ! value abusively, which matches the false.

Meta: @fpagnoux @MattiSG What could we do to avoid this from now?

Graph view doesn't work.

• Add the logo.
• Integrate source version under the logo.
• Count total visible formulas & parameters as a description of the system: OpenFisca référence {{ count }} formules et {{ count }} paramètres qui modélisent le système socio-fiscal français..
• Remove breadcrumbs bar.
• Remove the graph link.
• Remove the nav bar.
• Increase readability of list items: title is variable name, description is its label.
• Make everything bigger.
• Remove direct links to GitHub.

Two main concerns:

• wrong search on the name (class) of the variable. Exemple: Prime pour l'activité find ppa but ppa doesn't succeed to find ppa
• Displaying the results of the search should be enhanced (larger display zone) to avoid horizonthal scroll bar as much as possible

This issue was randomly assigned. Feel free to change those ;-)

Add a new view for organizations, ie http://legislation.openfisca.fr/organization/acoss which displays the variables and parameters tagged by organization = accos.

Replace “Back to home” button in the detailed view of a variable with a “Back” button that saves my search.

Run #63 in continuous integration.

Some formulas call external functions (ie csg_deductible_chomage calls montant_csg_crds).

The source code of these functions should be displayed in the tool.

Use SauceLabs.

Links displayed in both web pages and JSON data point to the wrong place, example:

{
defaultValue: 0,
definitionPeriod: "MONTH",
description: "SMIC proratisé (mensuel)",
entity: "individu",
formulas: {
0001-01-01: {
content: "def function(self, simulation, period): coefficient_proratisation = simulation.calculate('coefficient_proratisation', period) smic_horaire_brut = simulation.legislation_at(period.start).cotsoc.gen.smic_h_b smic_proratise = coefficient_proratisation * smic_horaire_brut * 35 * 52 / 12 return smic_proratise ",
source: "https://github.com/openfisca/openfisca-france/blob/18.2.0ckages/openfisca_france/model/prelevements_obligatoires/prelevements_sociaux/cotisations_sociales/allegements.py#L296-L301"
}
},
id: "smic_proratise",
source: "https://github.com/openfisca/openfisca-france/blob/18.2.0ckages/openfisca_france/model/prelevements_obligatoires/prelevements_sociaux/cotisations_sociales/allegements.py#L290-L301",
valueType: "Float"
}

Get parameters list from the prerelease API endpoint.

The barèmes won't have values for the moment, that's ok.

Example: go to http://legislation.openfisca.fr/variables/ppa and click on "GitHub" beside the source code of the variable

As an analyst,
I know if I can provide a variable value on a different period than its definition one and how the engine will expand it,
So that I don't get surprises when I request a computation

Parse, expose, show and document set_input values.

As a Producer,
I don't see a “Formules utilisant ce paramètre : aucunes” label in a parameter detailed view,
So that I am not misled thinking it is true while it's the consequence of a bug in the parsers

Cover the legislation explorer with tests that prove:

• The page loads and shows metadata on the loaded tax and benefit system.
• The search does filter the list.
• Navigating to an item of the list shows details.
• Going back keeps the search.

When I'm on the ir.bareme parameter page I'd like to see the JSON representation of the parameter.

As a reuser,
I can search for a term in the label of variables,
To identify a specific variable

Look for strict inclusion of the looked for substring in the variable name.

Extends #22.

It would be nice to have a clear label instead of aefa.py etc in the variables explorer.

What is the better way to obtain that ?
Should we add a label variable in all the modules containing variables ?

The thresholds are inverted, they define start values, not end.

http://legislation.openfisca.fr/parameters/ir.bareme

As the search box with auto-completion in the graph.

-> to a better UX of the legilsation-explorer

Deploy the legislation explorer latest version on every commit to master.

Follows #37.

As a legislation explorer user typing "salaire base" in the search field,
I get the variable "salaire_de_base" in my results

The formula rsa_base_ressources calls the formula rsa_base_ressources_individu.

But rsa_base_ressources does not appear in the caller variables ("variables appelantes" in french) of rsa_base_ressources_individu.

It is very probably due to the fact that rsa_base_ressources is a DatedVariable.

Example: https://legislation.openfisca.fr/variables/f7wt displays start date but not stop date

When you click for the first time on a variable you get in spite of the top of the page (at the beginning) to the end of the page

Design and implement a new view for variables.

• Increase the description font size.
• Update the sentence to (notice bold):

Cette variable s'applique aux entités individu / foyer fiscal / ménage / famille.
Elle a une période de définition d'un mois / d'un an / qui est l'éternité. Sa valeur est fixe dans le temps.
Sa valeur est un entier / un nombre décimal / une date (for unmapped types, default to showing them directly).
Sa valeur par défaut est 0 / 0.0 / 01/01/0001.

• Add a source code link at the end of each formula with name “Modifier cette formule”.
• Rename the source code link to “Modifier ces informations”.
• For variables with no formula, remove title “Formule de calcul” and add the following text to its details:

Elle n'a pas de formule et n'est donc pas calculable. Elle ne peut qu'être fournie en entrée lors d'un calcul.

• Localize all of the textual elements.
• Remove the “external link” icons.

As a producer,
I can search for an entity type in the legislation explorer,
So that I can get all necessary information to code formulas in a single place

As an analyst,
I can read the definition period of a variable,
So that I know on which periods I can call it

• Consume the data provided by openfisca/openfisca-web-api#125.
• Remove all references to the former API.
• Make the “definition period” header a link to the periods documentation page.

As an OpenFisca reuser,
I can understand the expected result of the search button,
So that I save a seconds on my first interactions

• The “Trouver” button should be in a contrast color.
• The “En savoir plus” button should be a link.
• The logo should be smaller.

The data source should be the latest available version of OpenFisca on PyPI.

http://legislation.openfisca.fr/variables/redevable_taxe_apprentissage

When you click on that line link :

Include the following text, above the count of parameters and variables, with language depending on the browser language:

en

OpenFisca makes law computable. It is a free and open-source computation engine that allows modelling tax and benefit systems in a collaborative and transparent way. This software is used by researchers and public agencies.

fr

OpenFisca rend le droit calculable. Il s’agit d’un moteur de calcul libre et ouvert qui permet de modéliser le système socio-fiscal de manière collaborative et transparente. Ce logiciel est utilisé par des chercheurs en économie et des services publics.