{"action":"created","issue":{"url":"https://api.github.com/repos/IIIF/discovery/issues/37","repository_url":"https://api.github.com/repos/IIIF/discovery","labels_url":"https://api.github.com/repos/IIIF/discovery/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/IIIF/discovery/issues/37/comments","events_url":"https://api.github.com/repos/IIIF/discovery/issues/37/events","html_url":"https://github.com/IIIF/discovery/issues/37","id":340344964,"node_id":"MDU6SXNzdWUzNDAzNDQ5NjQ=","number":37,"title":"Collect \"attribution\" use cases from various perspectives","user":{"login":"azaroth42","id":871868,"node_id":"MDQ6VXNlcjg3MTg2OA==","avatar_url":"https://avatars3.githubusercontent.com/u/871868?v=4","gravatar_id":"","url":"https://api.github.com/users/azaroth42","html_url":"https://github.com/azaroth42","followers_url":"https://api.github.com/users/azaroth42/followers","following_url":"https://api.github.com/users/azaroth42/following{/other_user}","gists_url":"https://api.github.com/users/azaroth42/gists{/gist_id}","starred_url":"https://api.github.com/users/azaroth42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/azaroth42/subscriptions","organizations_url":"https://api.github.com/users/azaroth42/orgs","repos_url":"https://api.github.com/users/azaroth42/repos","events_url":"https://api.github.com/users/azaroth42/events{/privacy}","received_events_url":"https://api.github.com/users/azaroth42/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":15,"created_at":"2018-07-11T17:54:00Z","updated_at":"2018-07-12T15:23:06Z","closed_at":null,"author_association":"MEMBER","body":"In order to better understand which metadata properties should be part of which documents (discovery, presentation, or external metadata), we need to understand the use cases for how those properties will be used, by which actors in the ecosystem.\r\n\r\nThis issue is to collect use cases around the relationship between organizations (or other actors) and the resources, in particular the AS Collection, AS Activity, IIIF Collection and IIIF Manifest.\r\n\r\nActors:\r\n * Aggregator:  The organization that collects IIIF resources, and exposes a search engine for them\r\n * Content Publisher: The organization that publishes the IIIF resources\r\n * End User: The user of the Aggregator, to discovery the Resources, who then interacts with them.\r\n"},"comment":{"url":"https://api.github.com/repos/IIIF/discovery/issues/comments/404550501","html_url":"https://github.com/IIIF/discovery/issues/37#issuecomment-404550501","issue_url":"https://api.github.com/repos/IIIF/discovery/issues/37","id":404550501,"node_id":"MDEyOklzc3VlQ29tbWVudDQwNDU1MDUwMQ==","user":{"login":"beaudet","id":77699,"node_id":"MDQ6VXNlcjc3Njk5","avatar_url":"https://avatars1.githubusercontent.com/u/77699?v=4","gravatar_id":"","url":"https://api.github.com/users/beaudet","html_url":"https://github.com/beaudet","followers_url":"https://api.github.com/users/beaudet/followers","following_url":"https://api.github.com/users/beaudet/following{/other_user}","gists_url":"https://api.github.com/users/beaudet/gists{/gist_id}","starred_url":"https://api.github.com/users/beaudet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/beaudet/subscriptions","organizations_url":"https://api.github.com/users/beaudet/orgs","repos_url":"https://api.github.com/users/beaudet/repos","events_url":"https://api.github.com/users/beaudet/events{/privacy}","received_events_url":"https://api.github.com/users/beaudet/received_events","type":"User","site_admin":false},"created_at":"2018-07-12T15:23:06Z","updated_at":"2018-07-12T15:23:06Z","author_association":"NONE","body":"@azaroth42 - Yes, that was intentional actually.  I don't think chopping up use cases so they're laser focused on a specific requirement is the best approach here because it can result in the overall use case being forgotten.  I understand you're probably looking to highlight the portions that are relevant to the particular topic being discussed, in this case, the relevance to the \"attributed to\" property at one or more levels within an activity stream.  I think that can be done while maintaining the overall use case context, but since we're using Github to document these things, I'm wondering how you think it best to proceed here.  For example, should I document the overall use case in another issue and then reference it from the reformulated language in this ticket?  Thanks."}}
{"actor":{"display_login":"beaudet"}}