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 property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(257) : eval()'d code PHP 8.0.30 (Linux)
File Line Function
/printthread.php(257) : eval()'d code 2 errorHandler->error
/printthread.php 257 eval
/printthread.php 117 printthread_multipage
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
Post Ex - 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: Post Ex (/showthread.php?tid=571)

Pages: 1 2 3


Post Ex - Curator Kid - 1st November 2007

I tend to do the same sort of thing as HB, although there are lots of exceptions - developments work in different ways so it's not always possible to pursue the same process all the time, and there isn't a "one size fits all" approach. Some large sites - especially minerals extraction ones - last for years. Bits and pieces have to be signed off as and when, with post-ex and publication a long way off, so I guess I'd be doing the same as Vulpes and ML there. It's a question of getting the wording right in any letters sent, and explicitly specifying that the overall archaeological conditions [u]should not </u>be discharged.

To go back to Trowelhead's original question - my heart sinks when I'm told that the post-ex for any site is to be put out to tender. I've [u]never </u>had a satisfactory result from this process, and it involves a lot of pointless work and wasted time to get to the same end result.


Post Ex - 1man1desk - 2nd November 2007

Posted by Kevin Wooldridge:
Quote:quote:...and surely a developer isn't beholden to the same contractor who undertook the field work to also carry out post-excavation work.
That depends on the contract they have signed. All of the specs and associated contract documents drawn up in my organisation cover both fieldwork and post-ex, so that from the outset the developer is tied-in contractually to paying for the post-ex, and keeping it with the original contractor.

Posted by Curator Kid:
Quote:quote:my heart sinks when I'm told that the post-ex for any site is to be put out to tender. I've never had a satisfactory result from this process
Maybe so - but you don't always get a satisfactory result from keeping the work with the original contractor either.
To my mind, the main advantage of keeping the post-ex in the same unit that did the fieldwork is that you retain the knowledge and understanding of the site held in the head of the person who was in charge on site. If they have moved employer, or are sent out on site again while someone else does the digging, where's the advantage? That is why our specs and contract documents try to tie the contractor down to using the original excavator as the main author of the report.

1man1desk

to let, fully furnished