Brian,
My tool is designed so that if a placement is made without custom
parameters, my tool will guide the instructor through selecting what
assessment should be associated with that placement (what Chuck called
resource_link_id configuration). This works great for an instructor
trying to set up their own content links.
Unfortunately, while I can use the same Tool in Canvas several times
to create multiple placements linked to different assessments, those
connections are based on the resource_link_id which, as Chuck
mentioned, is not included in a CC export, so all those links between
placements in Canvas and assessments on my system will not persist
across export/import.
Just the same, I tried making two placements in Canvas with the same
tool and exporting it. Only one LTI xml file was created, and neither
item in the organization section referenced it, which was odd. In the
module view, only one of the placements made with the tool showed up
after import, so one of them completely got lost in the export/import
process. As I suspected, the link between the placement and an
assessment on my system was lost in the process as well.
Your link selection extension seems like an interesting idea for
building courses that can be exported, though as discussed it might
make more sense to be setting a custom parameter rather than a
different URL.
David
On Jan 13, 12:28 pm, Brian Whitmer <
br...@instructure.com> wrote:
> David, sorry I wasn't clear. Adding a domain-matching tool wouldn't have
> any effect on the CC import process. I'm less familiar with our CC import
> process than I am with our LTI code, but I do know that tools and tool
> links are in separate models, that is probably reflected in the CC format
> somehow. I'd probably suggest building what you want by hand inside of a
> Canvas course, exporting the course as CC, and seeing what the difference
> is between that package and the one you're trying to import.
>
> Chuck, since you chimed in :-).
>
> I talked to Bracken and he finally convinced me that custom parameters on
> links *and* tools is an ok thing. I don't mean to be slow, it just takes me
> a while sometimes. My worry is the usability side of things. The reason I
> tend to push people to use query parameters on a URL is that at least in
> that case the user only has to copy and paste on "weird" value instead of
> two (a URL and custom parameters) when inserting a link.
>
> My ideal preference would be that the instructor wouldn't have to do any
> copy and pasting at all. That's what I'm shooting for with the "Link
> Selection" extension you can see in our API docshttps://
canvas.instructure.com/doc/api/link_selection_tools.html. The admin