XPPL: Difference between revisions
(→Access) |
(→Access) |
||
| Line 96: | Line 96: | ||
* How to deal with copyright? Is there space to be creative with our licensing? [https://www.pagesmagazine.net/en/articles/notes-about-spamsoc/58cbdeb7bf07dc00b19b0b93 SPAMSOC style?] | * How to deal with copyright? Is there space to be creative with our licensing? [https://www.pagesmagazine.net/en/articles/notes-about-spamsoc/58cbdeb7bf07dc00b19b0b93 SPAMSOC style?] | ||
* Who can upload / download / read / write? Should people make user profiles? Can people stay anonymous? Would that be related to the search engine as the first access point? | * Who can upload / download / read / write? Should people make user profiles? Can people stay anonymous? Would that be related to the search engine as the first access point? | ||
=== Tunnels and protocols === | |||
* Playing with the accessibility by hiding parts in the network, separating the data in pieces, changing the names of the books depending on the annotations | |||
==Future== | ==Future== | ||
Revision as of 22:19, 14 May 2018
XPUB LIB
A digital library for students, by students.
Brainstorm Session 10.05.2018: https://pad.pzimediadesign.nl/p/xpub-library
Questions to answer:
- Who:
Who is using it? Only PZ? Who is contributing?
- What:
Most important features? Content?
- Where:
local? networked? physical/digital space?
- When:
temporary? always available? updating?
- Why:
what is the goal?
- How to make it interesting and expandable? How people are contributing?
Collecting the Library
Gathering information on the existing book shelf @ the studio
Also good to look into: Xpub reader
Saturday Session 12.05.2018: https://docs.google.com/spreadsheets/d/1A7Fn70y9Pf_uVacEeFzLkOtx9hU4OTRTd074dLuLjHw/edit#gid=0
Structure
Categories
- Tags?
- Thematic categories
- Allow users to make collections or 'stacks' - A stack is a number of books that are read at a certain point in time, alternating between them. They usually have a topic in common, or follow a certain study path that can bring you to a point of knowledge. Rather than a bookshelf, where books are lined up and often forgotten, the stack on your table/nightstand/toilet consists of books prone to be opened and reopened at any time.
- Cataloguing. An interesting way to search through them
Metadata
- What info to extract, to make visible?
- reference info: title, author, year, publisher, ISBN / DOI
- file format
- reading time?
- price?
- abstract?
- source?
- upload data (date, time, note?)
- other metadata related to the protocols (like the TCP/IP)
- annotations that have happened manually for the purpose of the protocols (like for DNS connected to IP)
Platform
?? What platform to use for the collection ??
- PI
- JSON / MySQL
- Mediawiki
- Calibre
Interface
Search?
- Search engine that allows for serendipity?
- Full text search?
- How the information after the search will be shown?
List / Items
- How to design a reading interface that situates the items and explores its provenance?
- e.g. searching for a non-existant item will create a placeholder for that item, every subsequent query is tracked, so you also can see the searched for books (wishlist) along with the existing books
Annotation System
- Human annotations in browser? As a separate layer to the books? Visible to everyone?
- Machine annotations?
Reading Time
https://pad.pzimediadesign.nl/p/itl-tools
Reading a pirate library in public space
Sociality
- What modes of sociality can we embed into a library interface? Can we devise new ways to talk back to the data?
- How to hero the enunciative materiality of an academic library? Prioritize ecosystems and interactions instead of objects?
- What role does media piracy play for students around the world? In Western and non-western contexts, who is the pirate downloader and the outlaw uploader?
- What kind of community do we want to build? What is the priority: P2P? Platform for mass sharing?
- Can we find ways to bring digital transactions + physical relationships together?
- More here
3D Steganography version of the library
Access
- Which parts of the library should be private and which public? How many layers do we want to design into the interface?
- How to deal with copyright? Is there space to be creative with our licensing? SPAMSOC style?
- Who can upload / download / read / write? Should people make user profiles? Can people stay anonymous? Would that be related to the search engine as the first access point?
Tunnels and protocols
- Playing with the accessibility by hiding parts in the network, separating the data in pieces, changing the names of the books depending on the annotations
Future
How to keep it alive?
Planning
- by the 13th of May: List books in PZI bookshelf and download PDF's of them
- categories / catalogue system
- access: how and who
- research visual interface
- by 15th May: wiki pages of our proposal with each person's focus
- plan survey / discussion with research station
- 13 June: PANIC IN THE STREETS OF LONDON, PANIC IN THE STREETS OF BIRMINGHAM, PANIC AT THE DISCO –––––––––– https://www.youtube.com/watch?v=wMykYSQaG_c
- 14 June: PRESENTATION OF PROTOTYPE
- 14 June: Hang the DJ