{"action":"created","issue":{"url":"https://api.github.com/repos/Islandora-CLAW/CLAW/issues/817","repository_url":"https://api.github.com/repos/Islandora-CLAW/CLAW","labels_url":"https://api.github.com/repos/Islandora-CLAW/CLAW/issues/817/labels{/name}","comments_url":"https://api.github.com/repos/Islandora-CLAW/CLAW/issues/817/comments","events_url":"https://api.github.com/repos/Islandora-CLAW/CLAW/issues/817/events","html_url":"https://github.com/Islandora-CLAW/CLAW/issues/817","id":305299195,"number":817,"title":"Explore modeling controlled vocabularies as taxonomy terms","user":{"login":"dannylamb","id":20773151,"avatar_url":"https://avatars3.githubusercontent.com/u/20773151?v=4","gravatar_id":"","url":"https://api.github.com/users/dannylamb","html_url":"https://github.com/dannylamb","followers_url":"https://api.github.com/users/dannylamb/followers","following_url":"https://api.github.com/users/dannylamb/following{/other_user}","gists_url":"https://api.github.com/users/dannylamb/gists{/gist_id}","starred_url":"https://api.github.com/users/dannylamb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dannylamb/subscriptions","organizations_url":"https://api.github.com/users/dannylamb/orgs","repos_url":"https://api.github.com/users/dannylamb/repos","events_url":"https://api.github.com/users/dannylamb/events{/privacy}","received_events_url":"https://api.github.com/users/dannylamb/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-03-14T19:32:04Z","updated_at":"2018-03-21T19:47:22Z","closed_at":null,"author_association":"NONE","body":"From the March 14th CLAW Call:\r\n\r\nUsing the taxonomy module to tag content with terms from controlled vocabularies could be used to alleviate the administrivia involved with managing a large number of content types with their associated fields.   This would break the restriction of one rdf mapping per content type, as well most other site functionality.  This means we'd be using terms to dictate functionality, for which there are plenty of third party modules available.\r\n\r\nIt seems like a slam dunk, but there are some considerations we'll have to hammer out first.  Most notably that terms are generally considered local, though we'd want them to reference the uris present in the controlled vocabulary we're using.  We'd also have to figure out how we can enrich our RDF with enough information derived from the terms so that information gets persisted in Fedora.  Most likely this means we'd be adding one or more `rdf:type`s to our jsonld based on what taxonomy terms a node is tagged with.\r\n\r\nFYI, we'll probably get a lot of mileage out of this: https://www.drupal.org/project/term_condition Aren't plugins beautiful?"},"comment":{"url":"https://api.github.com/repos/Islandora-CLAW/CLAW/issues/comments/375072677","html_url":"https://github.com/Islandora-CLAW/CLAW/issues/817#issuecomment-375072677","issue_url":"https://api.github.com/repos/Islandora-CLAW/CLAW/issues/817","id":375072677,"user":{"login":"seth-shaw-unlv","id":29869988,"avatar_url":"https://avatars0.githubusercontent.com/u/29869988?v=4","gravatar_id":"","url":"https://api.github.com/users/seth-shaw-unlv","html_url":"https://github.com/seth-shaw-unlv","followers_url":"https://api.github.com/users/seth-shaw-unlv/followers","following_url":"https://api.github.com/users/seth-shaw-unlv/following{/other_user}","gists_url":"https://api.github.com/users/seth-shaw-unlv/gists{/gist_id}","starred_url":"https://api.github.com/users/seth-shaw-unlv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/seth-shaw-unlv/subscriptions","organizations_url":"https://api.github.com/users/seth-shaw-unlv/orgs","repos_url":"https://api.github.com/users/seth-shaw-unlv/repos","events_url":"https://api.github.com/users/seth-shaw-unlv/events{/privacy}","received_events_url":"https://api.github.com/users/seth-shaw-unlv/received_events","type":"User","site_admin":false},"created_at":"2018-03-21T19:47:22Z","updated_at":"2018-03-21T19:47:22Z","author_association":"NONE","body":"Trying to wrap my head around this, so I may be way off base, but let me see if I'm reading this right...\r\n\r\nCurrently we have a content model that stores descriptive metadata as part of the node with media entity references for each of the file representations (tiff, th, web_content, etc.). This is serialized into json-ld with the help of RDF Mappings and serves as the basis for what Fedora 4 receives and stores.\r\n\r\nWith context: would have a suite of fields available, not necessarily associated with any particular content type/bundle, but with a taxonomy term context that would trigger their availability for a given node?\r\n\r\nFor example, I have this node with the taxonomy terms \"image\" and \"dublin core\" applied to it, so _magically_ that node would then have the fields corresponding to each taxonomy term? (E.g. a tiff media entity reference for the image term and dc:date and dc:extent for the dublin core term.)\r\n\r\nIs that a correct characterization or am I misunderstanding how context would be used?"}}
{"actor":{"display_login":"seth-shaw-unlv"}}