{"action":"created","issue":{"url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/787","repository_url":"https://api.github.com/repos/ManifoldScholar/manifold","labels_url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/787/labels{/name}","comments_url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/787/comments","events_url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/787/events","html_url":"https://github.com/ManifoldScholar/manifold/issues/787","id":295186620,"number":787,"title":"Compose resources from smaller components, rather than strictly defining types","user":{"login":"zdavis","id":255909,"avatar_url":"https://avatars3.githubusercontent.com/u/255909?v=4","gravatar_id":"","url":"https://api.github.com/users/zdavis","html_url":"https://github.com/zdavis","followers_url":"https://api.github.com/users/zdavis/followers","following_url":"https://api.github.com/users/zdavis/following{/other_user}","gists_url":"https://api.github.com/users/zdavis/gists{/gist_id}","starred_url":"https://api.github.com/users/zdavis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zdavis/subscriptions","organizations_url":"https://api.github.com/users/zdavis/orgs","repos_url":"https://api.github.com/users/zdavis/repos","events_url":"https://api.github.com/users/zdavis/events{/privacy}","received_events_url":"https://api.github.com/users/zdavis/received_events","type":"User","site_admin":false},"labels":[{"id":824204541,"url":"https://api.github.com/repos/ManifoldScholar/manifold/labels/feature%20request","name":"feature request","color":"1d76db","default":false},{"id":577649372,"url":"https://api.github.com/repos/ManifoldScholar/manifold/labels/under%20discussion","name":"under discussion","color":"c5def5","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-07T15:45:41Z","updated_at":"2018-04-19T15:51:59Z","closed_at":null,"author_association":"OWNER","body":"## Feature Description\r\nThe purpose of this issue is to track a set of improvements to resources that we might want to tackle at once in a future release. Resources display in five principle ways: 1) as a slide in a collection slideshow, 2) as a card in a resource list, 3) in an overlay within the reader, 4) as a marginal note in the reader, and 5) on its detail page. Currently, we have some switching logic that changes the display of each mode depending on the resource kind and sub-kind. Some degree of switching logic is necessary, because we have to make choices about what to display. In the hero on the detail view, for example, we can't really show both a video and a file download link.\r\n\r\nThat said, I think it would be wise to move toward a system where we come up with a more systematic approach. For example, it might make sense to build resource \"hero\" models that can be of a fixed number of types: video, audio, or image, for example. It might make sense to allow any resource to have any kind of hero—that way, a file resource (say, a downloadable .exe of a video game), could be accompanied by a video hero that showed an example of the game play. I think it would also make sense to expose the thumbnail field across all resources and have it work in a consistent way. I think we ought to offer downloadable attachments on all resources, not just on ones that are specifically meant to be downloaded. We might also want to consider treating links the same as attachments. That is, as add-ons that can be included with any resource and that display if present. With a more flexible approach to attachments and links, we should be able to get to a place where a \"spreadsheet\" resource could be either an attached Excel file, or a linked Google Sheet.\r\n\r\n## *Why* is this feature important? *Who* does it help?\r\nWe want to fully support authors and presses, and a wide variety of resources. The constraints of the current approach seem arbitrary in places.\r\n\r\n## User Stories\r\nThe following stories are not meant to be exhaustive. Rather, they attempt to capture some requests that have come on in relation to this issue.\r\n\r\n- As an admin or author managing resources...\r\n    -   I can add a thumbnail to a file resource.\r\n    -   I can include a video or audio preview on a file resource.\r\n    -   I can offer multiple attached files for download on any resource kind.\r\n    -   I can link spreadsheet resources to google sheets, documents to google docs, etc.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/comments/382786981","html_url":"https://github.com/ManifoldScholar/manifold/issues/787#issuecomment-382786981","issue_url":"https://api.github.com/repos/ManifoldScholar/manifold/issues/787","id":382786981,"user":{"login":"tsmyre","id":25825222,"avatar_url":"https://avatars1.githubusercontent.com/u/25825222?v=4","gravatar_id":"","url":"https://api.github.com/users/tsmyre","html_url":"https://github.com/tsmyre","followers_url":"https://api.github.com/users/tsmyre/followers","following_url":"https://api.github.com/users/tsmyre/following{/other_user}","gists_url":"https://api.github.com/users/tsmyre/gists{/gist_id}","starred_url":"https://api.github.com/users/tsmyre/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tsmyre/subscriptions","organizations_url":"https://api.github.com/users/tsmyre/orgs","repos_url":"https://api.github.com/users/tsmyre/repos","events_url":"https://api.github.com/users/tsmyre/events{/privacy}","received_events_url":"https://api.github.com/users/tsmyre/received_events","type":"User","site_admin":false},"created_at":"2018-04-19T15:51:59Z","updated_at":"2018-04-19T15:51:59Z","author_association":"NONE","body":"As part of this revised approach, I think it would be useful to have variants made available for File Resources (or perhaps for all resource kinds generally). In situations where authors have prepared apps for different operating systems, it would be nice to be able to provide any alternatives that exist as part of the same resource instead of creating secondary ones. Having custom thumbnails available to those variants would useful as well in situations where it is important to distinguish between file types in visual mannger (e.g., the Apple logo against the Linux penguin). "}}
{"actor":{"display_login":"tsmyre"}}