The following warnings occurred:
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.0.30 (Linux)
File Line Function
/global.php 783 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.0.30 (Linux)
File Line Function
/global.php 783 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined variable $awaitingusers - Line: 34 - File: global.php(844) : eval()'d code PHP 8.0.30 (Linux)
File Line Function
/global.php(844) : eval()'d code 34 errorHandler->error
/global.php 844 eval
/printthread.php 16 require_once
Warning [2] Undefined array key "style" - Line: 909 - File: global.php PHP 8.0.30 (Linux)
File Line Function
/global.php 909 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined property: MyLanguage::$lang_select_default - Line: 5010 - File: inc/functions.php PHP 8.0.30 (Linux)
File Line Function
/inc/functions.php 5010 errorHandler->error
/global.php 909 build_theme_select
/printthread.php 16 require_once
Warning [2] Undefined array key "additionalgroups" - Line: 7045 - File: inc/functions.php PHP 8.0.30 (Linux)
File Line Function
/inc/functions.php 7045 errorHandler->error
/inc/functions.php 5030 is_member
/global.php 909 build_theme_select
/printthread.php 16 require_once
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error



BAJR Federation Archaeology
informed curators - Printable Version

+- BAJR Federation Archaeology (http://www.bajrfed.co.uk)
+-- Forum: BAJR Federation Forums (http://www.bajrfed.co.uk/forumdisplay.php?fid=3)
+--- Forum: The Site Hut (http://www.bajrfed.co.uk/forumdisplay.php?fid=7)
+--- Thread: informed curators (/showthread.php?tid=29)



informed curators - the invisible man - 15th October 2005

I think that's their job. From where they sit, I suppose you are actually part of the bird-pooh/grain matrix.

We've done it to death before, but a licensing system of some sort might give them more teeth.

Today, Bradford. Tomorrow, well, Bradford probably.


informed curators - troll - 15th October 2005

I do think that licensing certainly has legs-but also has a few problems as our colleagues on the Emerald Isle have repeatedly pointed out.I mentioned some time ago that it would be good to see curators taking an interest in the views of coal-face types on site visits.If you really want to know about a car, ask a mechanic-not a car salesperson.Big Grin


informed curators - monitor lizard - 17th October 2005

Troll haven't we been here before?

Good curators ask, or at least can assess a situation without asking. Good units encourage this - I know of many who are more than happy for me to conduct monitoring visits without senior staff present (personally, I don't like this as it can lead to headache if things need to be changed or there's a problem), but I guess that means they trust their staff, or units where the person digging the features is expected to explain what they are digging, what they have found and why.

But as has also been brought up before, we see a lot of sites - and have worked on a lot too - and it doesn't take too many years on the beat to separate the 'bird-pooh' from the grain without talking to everyone out there and their dog - and who has the time for that?

And to look at it from the other side, how many diggers really want to talk to us? Most seem to hide in the hut when I come around, or at least duck into their trenches looking busy but only grunt when spoken to. I suspect that is because there's little confidence among junior staff members, and that is probably a factor of the situation they learn in.

Ranting over.

ML


informed curators - Hugh - 17th October 2005

If I had a potential problem with a contracting unit I would start by asking the curators in surrounding authorities what their experiances of the unit were. This would be followed up by a intensive site visit with an attempt to talk to the diggers and super etc.
However I would not bother myself about things like interpersonal skills, just health and safety and excavation techniques etc. The later of these could produce sub-standard reports which I would reject which would cause the planning condition to stay attached to the development. This would basically cause a breach of condition as the archaeology could not be re-instated, and the cost of the fine would end up on the desk of the contractor for causing the breach. This would stop them doing it again, one way or another.

Personally I would only need help on this from my fellow curators, but cheers for the thought.

Where?