# Arc Editor Failed LocoKit Import

**URL:** <https://support.bigpaua.com/t/arc-editor-failed-locokit-import/1033>\
**Category:** Arc App Support\
**Created:** [20 October 2025 02:54 UTC](https://support.bigpaua.com/t/arc-editor-failed-locokit-import/1033 "2025-10-20T02:54:39Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![DotKern](https://dub1.discourse-cdn.com/flex013/user_avatar/support.bigpaua.com/dotkern/32/877_2.png) [@DotKern](https://support.bigpaua.com/u/DotKern)\
**Post date:** [7 November 2025 08:21 UTC](https://support.bigpaua.com/t/arc-editor-failed-locokit-import/1033/21 "2025-11-07T08:21:23Z")

</div>

Could you explain in more technical terms how the notes work? I assumed it was just field on the data but then I accidentally added two. How are they stored? Are they exportable? When exported how are they linked to locations? How simple would implementing basic markdown in them be? Thanks!

---

<div class="post-metadata">

**Author:** ![matt](https://dub1.discourse-cdn.com/flex013/user_avatar/support.bigpaua.com/matt/32/3_2.png) [@matt](https://support.bigpaua.com/u/matt)\
**Post date:** [8 November 2025 03:26 UTC](https://support.bigpaua.com/t/arc-editor-failed-locokit-import/1033/22 "2025-11-08T03:26:49Z")

</div>

> [@DotKern](#):
>
> Could you explain in more technical terms how the notes work?

Sure thing!

> [@DotKern](#):
>
> I assumed it was just field on the data but then I accidentally added two. How are they stored?

They’re stored as a separate Notes table in the database, which have … actually let me check the schema…

```swift
try db.create(table: "Note") { table in
    table.primaryKey("id", .text)
    table.column("lastSaved", .datetime).notNull().defaults(sql: "CURRENT_TIMESTAMP")
    table.column("source", .text).notNull().indexed()

    table.column("creationDate", .datetime).notNull()
    table.column("startDate", .datetime).notNull().indexed()
    table.column("endDate", .datetime).notNull().indexed()
    table.column("deleted", .boolean).notNull()

    table.column("body", .text).notNull()

    table.column("timelineItemId", .text).indexed()
        .references("TimelineItemBase", onDelete: .setNull, deferred: true)
}

```

Ok so “body” is the content of the note, and its relationship to TimelineItems is by an option reference to the item’s id, to associate it with the item that it was added from.

It also has date values, which the UI can also use to show any notes that fall within an item’s date range, even if the notes aren’t directly associated with the item by id. (That’s actually a bug I’m fixing today - they were losing that item id reference when items got merged during processing).

So notes can either appear under an item by direct reference to the item’s id, or by virtue of falling within the item’s date range.

> [@DotKern](#):
>
> Are they exportable? When exported how are they linked to locations?

I hope they’re exportable! though I’m uncertain on whether they’re included in the current JSON exports. I’ll check that now… Oh dear, they’re not! I’ll put that on the todos as high priority.

> [@DotKern](#):
>
> How simple would implementing basic markdown in them be?

My instinct is to say “not too difficult”, but the devil will be in the details I think. Like, parsing Markdown for presentation is trivial and essentially built in to SwiftUI these days. But the actual editor would require considerable complexity. But I’m guessing that’s something that’s already been built many times, and is available out there on Github, ready for reuse.

---

<div class="post-metadata">

**Author:** ![DotKern](https://dub1.discourse-cdn.com/flex013/user_avatar/support.bigpaua.com/dotkern/32/877_2.png) [@DotKern](https://support.bigpaua.com/u/DotKern)\
**Post date:** [8 November 2025 21:50 UTC](https://support.bigpaua.com/t/arc-editor-failed-locokit-import/1033/23 "2025-11-08T21:50:00Z")

</div>

> [@matt](#):
>
> Like, parsing Markdown for presentation is trivial and essentially built in to SwiftUI these days. But the actual editor would require considerable complexity. But I’m guessing that’s something that’s already been built many times, and is available out there on Github, ready for reuse.

Yeah that was my initial thought but I imagine getting tool bars and _nice_ functionality would be a bit more difficult. And y’know if you built it you might as well built it right, with smart brackets and auto hide for text formatting, etc.  
Anyways, I’ll put this all over on changemap when I get a good break from life’s other battles.

---

<div class="post-metadata">

**Author:** ![matt](https://dub1.discourse-cdn.com/flex013/user_avatar/support.bigpaua.com/matt/32/3_2.png) [@matt](https://support.bigpaua.com/u/matt)\
**Post date:** [10 November 2025 02:52 UTC](https://support.bigpaua.com/t/arc-editor-failed-locokit-import/1033/24 "2025-11-10T02:52:30Z")

</div>

Yeah Changemap feels like a good place for it. If it gets enough votes over there it essentially becomes a lock - it’s gonna get built. I’ve got a feeling there’s also some other entries there of the “improve notes / journaling” type. Worth voting on those too!

[Previous page](https://support.bigpaua.com/t/arc-editor-failed-locokit-import/1033.md?page=1)