Would you give me guidance on this?Īt this point I’m wondering, if no TSV export is needed, then is it ok to change the “Template:” field for “Container” to /Templates/CSV Page I’ve searched for a setting for this but am unable to find it. In the meantime, I notice that the notes in your file always show the "Text’, “Preview” and "Export tabs above the Note’s name, whereas the tabs on my Notes disappear shortly after the Note is made. I’ll go through your writings and put them together in a way that makes sense for me in terms of a step-by-step approach that I’m sure will generate a few more questions later on.
So, I did have the file I needed but didn’t know it. AT2 does import the file and presents its contents properly.įor the “TSV agent” a dialogue box entitled “HTML Export Folder” that has a Save As option “TSV_agent.txt”. Viewing via spreadsheet this file has the proper Attribute headers and the columns are properly populated with the corresponding Attribute values. What out put do you get.” A dialogue box entitled “HTML Export Folder” that has a Save As option “Container.html.”įor ‘CSV Export agent’ a dialogue box entitled “HTML Export Folder” that has a Save As option “CSV_Export_Agent.csv”. “Select note “Container” and use File ▸ Export Selected Note. If a container is only ever going to be used for one type of (non-HTML) export then it is a good idea to set the exported files name and extension via the Export Inspector: Tip: By placing prototypes inside the /Prototypes container you are less likely to make errors as above, although there is no formal requirement to do this. Using consistent case in the names of templates, especially when used ‘paired’ as here. Also, only add $Text to templates after you’ve set the template otherwise you’ll need to reset the $Text. Template notes should ideally be unique across the current doc. Tip: make new templates as siblings, then demote them. Nesting templates is a visual organisational affordance, but note whilst the /Template' container’s OnAdd sets the ‘HTML’ prototype for new notes, for children of such notes you will need to set the prototype manually. You’d also got naming errors with some templates (names are case-sensitive. The main reason your export failed is you had made the export container “Export Note Template” into a Template which was not appropriate.
I’ve added container and agent based examples. In the picture you will see the data exporting. It may be that that the fields in the AT Events Role tab should also be able to be mapped, but for now, in concept, these can be filled in manually.ĬSV Export Test1.tbx 13-00-51 1956×920 198 KB In other words, I’d like to use the conventional CSV mapping schema to import selected TB attributes and KeyAttributes into their logical counterparts in AT2/3. The latter field may need to be expanded somewhat. Nonetheless, what I’d like AT to do would be to take the Note Title and import it into the AT Event Title field import the TB Note’s date attributes into the comparable AT Events Range fields and import the Key Attributes of any Note into what would be the equivalent of the AT Event Values Tag field. Since TB exports in HTML and AT imports in CSV, I’m not sure if my needs can be addressed as this import/export problem seems to be a negative gating item. Unlike your April 17 post, I’m looking to export from TB to AT. My current need involves a multi decade storyline with multiple story arcs and multiple events. Hello Mark, I’m recently new to TB by a couple of weeks (much appreciation for your invaluable, updated reference site) and have used AT since it came out.
0 kommentar(er)
