ruangrupa/lumbung.space
ruangrupa/lumbung.space
1
0
Fork 1
Code Issues 11 Pull Requests Projects Releases Wiki Activity

Make card for books.lumbung.space #35

New Issue
Closed
opened 2022-02-11 10:22:04 +00:00 by simoon · 7 comments
simoon commented 2022-02-11 10:22:04 +00:00
Owner
Copy Link

Card design needs to be made in Figma

Card design needs to be made in Figma
simoon self-assigned this 2022-02-11 10:22:04 +00:00
decentral1se added this to the (deleted) project 2022-02-11 10:29:15 +00:00
r commented 2022-02-11 17:42:04 +00:00
Member
Copy Link
{'title': 'TAGLINE FOR ARTISTIC SOCIETY',
 ' 'updated': '2021-12-09T06:55:05+00:00',
 'authors': [{'name': 'Reinaart Van Hoe'}],
 'tags': [{'term': 'creative commons',
   'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html',
   'label': 'creative commons'},
  {'term': 'open access',
   'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html',
   'label': 'open access'},
  {'term': 'public',
   'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html',
   'label': 'public'},
  {'term': 'publish',
   'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html',
   'label': 'publish'},
  {'term': 'ruangrupa',
   'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html',
   'label': 'ruangrupa'}],
 'summary': 'Material: Book, Size: 14x9 cm, 50 pages, Year: 2015 Some notes and conversations between Julia Sarisetiati and Reinaart Vanhoe on TAGLINE FOR ARTISTIC SOCIETY: A video made by Julia Sarisetiati. More: https://vimeo.com/148195791',
 'links': [{'type': 'image/jpeg',
   'href': 'https://books.lumbung.space/opds/cover/3',
   'rel': 'http://opds-spec.org/image'},
  {'type': 'image/jpeg',
   'href': 'https://books.lumbung.space/opds/cover/3',
   'rel': 'http://opds-spec.org/image/thumbnail'},
  {'rel': 'http://opds-spec.org/acquisition',
   'href': 'https://books.lumbung.space/opds/download/3/pdf/',
   'length': '4244163',
   'mtime': '2021-12-09T06:55:05+00:00',
   'type': 'application/pdf'}

This is the data than can potentially be represented.

In addition there are also fields such as publisher. Have a look at the metadata of a book in for more details https://books.lumbung.space/

However, the design should also work when particular fields are missing.

An open question is whether to link to the file or just link to the book entry on books.lumbung.space

``` {'title': 'TAGLINE FOR ARTISTIC SOCIETY', ' 'updated': '2021-12-09T06:55:05+00:00', 'authors': [{'name': 'Reinaart Van Hoe'}], 'tags': [{'term': 'creative commons', 'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html', 'label': 'creative commons'}, {'term': 'open access', 'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html', 'label': 'open access'}, {'term': 'public', 'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html', 'label': 'public'}, {'term': 'publish', 'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html', 'label': 'publish'}, {'term': 'ruangrupa', 'scheme': 'http://www.bisg.org/standards/bisac_subject/index.html', 'label': 'ruangrupa'}], 'summary': 'Material: Book, Size: 14x9 cm, 50 pages, Year: 2015 Some notes and conversations between Julia Sarisetiati and Reinaart Vanhoe on TAGLINE FOR ARTISTIC SOCIETY: A video made by Julia Sarisetiati. More: https://vimeo.com/148195791', 'links': [{'type': 'image/jpeg', 'href': 'https://books.lumbung.space/opds/cover/3', 'rel': 'http://opds-spec.org/image'}, {'type': 'image/jpeg', 'href': 'https://books.lumbung.space/opds/cover/3', 'rel': 'http://opds-spec.org/image/thumbnail'}, {'rel': 'http://opds-spec.org/acquisition', 'href': 'https://books.lumbung.space/opds/download/3/pdf/', 'length': '4244163', 'mtime': '2021-12-09T06:55:05+00:00', 'type': 'application/pdf'} ``` This is the data than can potentially be represented. In addition there are also fields such as publisher. Have a look at the metadata of a book in for more details https://books.lumbung.space/ However, the design should also work when particular fields are missing. An open question is whether to link to the file or just link to the book entry on books.lumbung.space
simoon commented 2022-02-14 15:42:58 +00:00
Author
Owner
Copy Link

I've made a basic design for the books card (see left card in attached PNG). The metadata in books.lumbung.space is written quite well, although this may not always be the case.

From 100% certain to uncertain, what we can expect to be there in the metadata and file system are:

  • Timestamp (when the file was updated)
  • Title
  • Authors
  • Cover IMG
  • Tags
  • Summary (Description of the contents)
  • What can be included on the card in the form of summaries will almost certainly have to be truncated to the point where it becomes illegible (see right card). It doesn't make much sense to include it on the card, if this is the case. Just my 2c

Publisher and Language could be important to include, but there is no way of knowing they will be in the metadata. The mockup accounts for all of the fields above (except the summary), and if the tags, cover image or authors aren't there, the design works as well.

Following this approach, it makes sense to link to the book entry, where readers can read the full summary, see details such as Publisher and Language (if there) as well as choose to read/download the PDF or EPUB etc.

I've made a basic design for the books card (see left card in attached PNG). The metadata in books.lumbung.space is written quite well, although this may not always be the case. From 100% certain to uncertain, what we can expect to be there in the metadata and file system are: * Timestamp (when the file was updated) * Title * Authors * Cover IMG * Tags * Summary (Description of the contents) * What can be included on the card in the form of summaries will almost certainly have to be truncated to the point where it becomes illegible (see right card). It doesn't make much sense to include it on the card, if this is the case. Just my 2c Publisher and Language could be important to include, but there is no way of knowing they will be in the metadata. The mockup accounts for all of the fields above (except the summary), and if the tags, cover image or authors aren't there, the design works as well. Following this approach, it makes sense to link to the book entry, where readers can read the full summary, see details such as Publisher and Language (if there) as well as choose to read/download the PDF or EPUB etc.
Screen Shot 2022-02-14 at 16.42.19.png
136 KiB
Screen Shot 2022-02-14 at 16.42.19.png
r commented 2022-02-15 10:21:05 +00:00
Member
Copy Link

Hi Simon, thanks for the sketch!

I actually disagree with your assesment of what can be expected. If you look at what is already on books.lumbung.space you see that descriptions are often provided and are also meaningful whereas tags are usually much less meaningful (they repeat the name of the author for example).

So I think it is best to de-emphasize the tags in the design and allow more space for (truncated) descriptions.

In addition, titles can be suprisingly long as can be lists of authors. Which is something the current design doesn't seem ready for.

Finally, the OPDS feed currently only returns a single author even for volumes with multiple, something to take in to account if you work directly from the data. I'm opening an upstream issue.

Hi Simon, thanks for the sketch! I actually disagree with your assesment of what can be expected. If you look at what is already on books.lumbung.space you see that descriptions are often provided and are also meaningful whereas tags are usually much less meaningful (they repeat the name of the author for example). So I think it is best to de-emphasize the tags in the design and allow more space for (truncated) descriptions. In addition, titles can be suprisingly long as can be lists of authors. Which is something the current design doesn't seem ready for. Finally, the [OPDS feed](https://https://books.lumbung.space/opds/books/letter/00) currently only returns a single author even for volumes with multiple, something to take in to account if you work directly from the data. I'm opening an upstream issue.
simoon commented 2022-02-15 13:56:55 +00:00
Author
Owner
Copy Link

Thanks for your feedback, Roel & I agree with your argument for de-emphasising tags and allowing more space for titles and truncated descriptions.

Perhaps the author field should not be included at all if it means that multiple authors are ignored by the OPDS feed? Alternatively, if it was at all possible to use calibrestekje (a python bindings library that decentral1se wrote), you could also get multiple authors listed. I've had good success with this on this web app d1 & I made: Temporary Indexing.

Thanks for your feedback, Roel & I agree with your argument for de-emphasising tags and allowing more space for titles and truncated descriptions. Perhaps the author field should not be included at all if it means that multiple authors are ignored by the OPDS feed? Alternatively, if it was at all possible to use [calibrestekje](https://calibrestekje.readthedocs.io/en/latest/) (a python bindings library that decentral1se wrote), you could also get multiple authors listed. I've had good success with this on this web app d1 & I made: [Temporary Indexing](https://index.simonbrowne.biz).
r commented 2022-02-16 09:25:01 +00:00
Member
Copy Link

Perhaps the author field should not be included at all if it means that multiple authors are ignored by the OPDS feed?

No, I think the author of a publication is very relevant information so that info should definitely be there! My warning was just that, if you would try it live, every book currently returns only one author due to the bug, but we should make space for multiple in fact!

I'm also opening an issue in calibre-web to have it fixed..

Thank you!

> Perhaps the author field should not be included at all if it means that multiple authors are ignored by the OPDS feed? No, I think the author of a publication is very relevant information so that info should definitely be there! My warning was just that, if you would try it live, every book currently returns only one author due to the bug, but we should make space for multiple in fact! I'm also opening an issue in calibre-web to have it fixed.. Thank you!
r commented 2022-02-16 15:02:19 +00:00
Member
Copy Link

ruangrupa/lumbunglib#26 This should help to pull the data in!

https://git.autonomic.zone/ruangrupa/lumbunglib/pulls/26 This should help to pull the data in!
decentral1se commented 2022-03-04 10:41:39 +00:00
Owner
Copy Link

We're gonna follow up in ruangrupa/lumbunglib#26 👍

Card has been designed.

We're gonna follow up in https://git.autonomic.zone/ruangrupa/lumbunglib/pulls/26 👍 Card has been designed.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
simoon
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ruangrupa/lumbung.space#35
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?