__AGENCY WEBSITE__

Issue tracker on gitlab: https://gitlab.constantvzw.org/agency/agency/-/issues
jinja templating


July 9 2021

to do list for Michael:
    - assembly shows first years, then name of assemblies, if one clicks on the assemby in intend can come the question that was tackled and then in intend the things that were exhibited
    - login refers to an email called info@agentive.be but it needs to be agentive.org
    
to do list Morgane:
    - list of boundary things shows a list, it would be nice that the not uploaded things that are not clicakble yet are listed in gray like in the other part of the website
    - list of boundary things, once click on a thing, then the title of the thing is not shown 
    -> because of the display none on the h1 -> need to find a solution in order to have other title appearing but not that one
    - indent for the subcategories in the assemblies
    - list of boundary things, once click on a thing, in the list of douments the title is there but in italic
    
to do Kobe:
    - uploading things    

May 25 2021

Michael: I am working on ...
  1. protected documents (publication) -- this will eventually also need a style (grayed out as well? or something else) Grey sounds good
  2. "login" page + functionality (will depend somewhat on how it technically works with the current server)
  3. title extraction (glitch with basque)
  4. images (also protected)

Questions

  1. There should probably be a link back to the "list of documents" page for a thing from a specific document. Currently it's just the menu which has no link that goes one step back.-> arrow 
  2. With Kobe, we talked about maybe not using italics to indicate links (some titles use italics to indicate a proper name / title) -- the "gray style" of the assembly pages seems maybe an alternative (or something like that?)
3. @Morgane: I added some styles to the list element in the assembly page (related to if the thing is linked or missing) and it seems to have activated some other styles so this may need adjustment (I could also change the name -- I think it's the "thing" class that's matching).
4. Assemblies page: in principle they should all be based on the EN layout (with years) (but currently only have the OverviewEng as a basis) .... what do show when no language specific version is available (currently there's a "simplified assembly list" ... but is this not confusing to also still have?)

Kobe:
    - list of assemblies in other languanges
    - finish the english list of assemblies
    - upload more folders of new things
    - think about logo?
    - think about cooperative membership ( check the templates/login.html )
    - Test login: "Mike Ditka" / password: powerfootball
    - Text to signal that some docs are only available if you are a member of the coop

Morgane






STUFF FROM BEFORE (May 2021)

Example:
Univesity of Cambridge might request a scan of some image material, but this would not entail costs of storage for instance, or for longer term maintenance of a server.

Example:
Ancient notions of "property" for instance of the forest. When a decision was made to clear trees to build a house, this was made based on the idea that the clearing would help maintain the forest. Thus the "property" related to the condition of the forest, rather than an abstract notion irrelvant to the forest itself and its care. (See also "Commons")

Example:
Images often have copyright meaning they can't be published, but they can be made visible (1) within a community, and (2) within an exhibition.

Traditional CMS / web platforms / wikis centralize resources on "cloud" servers / services.
* Located in a single centralized database
* Give access based on a rigid ginary of public or private

We propose the development of a COOCS (cooperative care system) (or CCCS (cooperative content care system))...
    * Based on distributed documents in a diversity of formats (tex, pdf, image)... and
    * from a variety of sources (e.g. legal documents from public sources, images that fall under copyright)
    * Peer to peer model for serving in different situations (offline / local networks)
    * Dealing with "gray zones" of giving access of materials that don't fit a strictly binary of public/private: provide different modes of access: public, community, editors, temporary access in the context of an exhibition...
    * Support for paid membership based on owning shares in the cooperative
    * Link access to care: Accessing the resources of the archive include taking responsibility for helping with the care of the archive

We propose making use of existing technologies / open-source tools:
* git
* latex
* pandoc
* Django
* emerging protocols like DAT or IPFS (?)
* ODOO https://www.odoo.com/


Biographies

PASTE HERE!!!

Born in 1994, Morgane Le Ferec is a graphic designer based in Brussels. In 2017 she co-founded a graphic design studio called D-E-A-L. She mainly works in the cultural filed and is active on the Brussels open source scene.

Name Morgane Le Ferec
Function Graphic designer
Vat number / registration number 94.03.18-664.15
Street + nr Rue Henri Wafelaerts, 52 
Postal code 1060 
City Brussels
Land Belgium
telnr 0495362922
e-mail morgane.leferec@gmail.com
sector graphic design
title representative (mr/mrs)
name representative
function representative