Assuming this thread is for the TBX side only (i.e. no changes to DTP metadata…)
User-defined mapping of TBX attributes to DTP tags.
If I take notes in TBX, then of course I keep data in discrete attributes ($Source, $Author, $BoolWhatever, $StrThingy and so on). When the time comes to export these notes to DTP, then I either lose this extra data, or I have to pre-process the notes to add the contents of the attributes to $Tags, so that they’re captured in DTPO. The TBX notes then contain redundant data.
It would be a nice feature if I could simply identify which attributes would be added to DTPO’s tags – automating the process I go through now.
Ideally the new tag would have a marker to to indicate the host attribute. e.g. $Source=“Bernstein2011” would become the DTPO tag Source==Bernstein2011  (thus facilitating DTP’s search and smart groups facilities).
For especially pleasing results it would be very nice if the return journey could disassemble the tag, so DTPO records with tags which begin with existing attributes could automatically (or be selected to) populate those attributes. (NextAction==Y --> $NextAction=true).
Of course, if you have enough influence to prod DevonTHINK in the direction of expanded user-defined metadata so these workarounds weren’t necessary, that would be even better .
Single click access to TBX notes from DTPO
I have no idea whether this is feasible or not so it’s probably a stupid idea but…
DTP’s excellence is in its AI and search, so there’s a great incentive to keep (or index) TBX files in DTPO. At the moment, AIUI it’s only the raw XML which is indexed, so that though a search will return results within the file, it’s not in a particularly friendly format to read, or easy to get to the original notes.
What about an optional ‘live’ index view (or separate file) on a TBX file, which could be indexed in DTPO instead, giving a subset of the data (Name, Text, user-selected attributes as dictionary pairs in the DTPO note text?) and a live link to the original note in the TBX file?
Apart from that…
From the previous comments in this thread – bi-directional sync I think is the most important improvement, and label/UUID/database/location info synchronisation (as bronco says, only the label number is needed) would be very welcome.
I think it’s great Eastgate are seeking feedback on this – DTPO and Tinderbox are made for each other and it’s welcome you’re actively looking to enhance the relationship… Thanks!
 I’ve used == as a marker for the DTP Attribute/content tag purely as an example. Unfortunately one of DTP’s failings is the inability to search on punctuation, but we could still do 'Starts with…" searches to group all Source information.