Order of next steps to publish the 'trilogy'

[j-hagedorn]

Hey @sdaranyi and @salmonix , I put the issues in our next milestone in an order which I think makes sense. Please let me know your thoughts, when you get the chance. Here's the basic idea:

1. Clean up the existing flattened files for the TMI and ATU
2. Merge the AT with ATU
3. Make the graph datasets based on the cleaned versions
4. Document it all
5. Clean up the AFT if possible

If any of these is unnecessary, please note it in the issue, and I'll gladly remove the issue from this milestone to streamline our work prior to the conference.

[sdaranyi]

Does this mean that you managed to merge the AT with the ATU, or we ignore that for now? The former would be quite a development. Sándor

…

On Thu, 18 Apr 2024 at 04:29, Joshh ***@***.***> wrote: Closed #47 <#47> as resolved. — Reply to this email directly, view it on GitHub <#47>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARZDKNV3N7332FOZXYAYROLY54VZVAVCNFSM6AAAAABCJV77ZCVHI2DSMVQWIX3LMV45UABFIRUXGY3VONZWS33OIV3GK3TUHI5E433UNFTGSY3BORUW63R3GEZDEOJVGIYQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[j-hagedorn]

No, we deprioritized that a few months back after my initial communication here.

[salmonix]

Which text shall be used for manual re-tagging? L.

…

On Thu, Apr 18, 2024 at 7:19 AM sdaranyi ***@***.***> wrote: Does this mean that you managed to merge the AT with the ATU, or we ignore that for now? The former would be quite a development. Sándor On Thu, 18 Apr 2024 at 04:29, Joshh ***@***.***> wrote: > Closed #47 <#47> as > resolved. > > — > Reply to this email directly, view it on GitHub > <#47>, or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ARZDKNV3N7332FOZXYAYROLY54VZVAVCNFSM6AAAAABCJV77ZCVHI2DSMVQWIX3LMV45UABFIRUXGY3VONZWS33OIV3GK3TUHI5E433UNFTGSY3BORUW63R3GEZDEOJVGIYQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.*** > com> > — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACKXK6XQLOUKP3532DVRQTY55JWTAVCNFSM6AAAAABCJV77ZCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNJQGQ3TA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[j-hagedorn]

@salmonix , do you mean for the ATU? The tale type descriptions are in 'atu_df'

[salmonix]

Not exactly. I want to add a manual resolution for ambiguous texts. See: branch notes_on_atu -> docs/ATU_NOTES.md
I would like to resolve the ambiguities manually.
Side not: what is the character encoding for the text files? On my Linux settings many accented characters are scrambled. Eg. data/atu_df.csv: "Hungarian: Gy�rgy" instead of "Hungarian: György"

[j-hagedorn]

I imagine you'd want the source text file referenced here: https://github.com/j-hagedorn/trilogy/blob/master/fetch/fetch_taletypes.R#L5

@sdaranyi may be able to provide it, or I can send once I'm at my computer.

Would love if you can identify the encoding issue so that I can fix those issues with characters!

[sdaranyi]

Sure if necessary.

…

On Sat, 20 Apr 2024 at 19:33, Joshh ***@***.***> wrote: I imagine you'd want the source text file referenced here: https://github.com/j-hagedorn/trilogy/blob/master/fetch/fetch_taletypes.R#L5 @sdaranyi <https://github.com/sdaranyi> may be able to provide it, or I can send once I'm at my computer. Would love if you can identify the encoding issue so that I can fix those issues with characters! — Reply to this email directly, view it on GitHub <#47 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARZDKNQHXFYE3VEHZWKILC3Y6KRFPAVCNFSM6AAAAABCJV77ZCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TCNZVGQ4TC> . You are receiving this because you were mentioned.Message ID: ***@***.***>