[O] Override :clock-in (hence org-clock-in) behavior for a specific capture template

[Cody Goodman]

Here is my detailed problem exposition exported from org:

1 executive summary
===================

  I want to start at a child node and clock into the grandparent rather than
  the current child at point in a capture task


2 my capture
============

  ,----
  | ("f" "video game" entry (file+olp+datetree "~/org/videoGameImprovement.org")
  |  "* %<%Y-%m-%d %H:%M>\n** game notes
  | *** %?
  | ** video(s)
  | *** video 1
  | **** note 1 for video 1
  | " :clock-in t)
  `----


3 what happens
==============

  I'm clocked into the place where `%?' takes me in the capture template


4 what I want to happen
=======================

  I want to land at the first child of the `game notes' node but clock
  into the `%<%Y-%m-%d %H:%M>' node 2 levels up


5 what I don't know how to do
=============================

5.1 In the capture template, I don't know how I could selectively use my own implementation of `org-clock-in'
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

5.1.1 Maybe I could have some sort of local binding surrounding just that capture which would be used?
------------------------------------------------------------------------------------------------------

* 5.1.1.1 advice?


* 5.1.1.2 is an `add-hook' possible only within a certain scope?

Thanks,

Cody