search

terraphim / terraphim-project

Product and project management for terraphim
GNU Affero General Public License v3.0
0 stars 0 forks source link

Terraphim release 0.1 use case #25

Open turkhale opened 9 months ago

turkhale commented 9 months ago

image

1. Study Terraphim Desktop setup on systems.tf and terraphim.ai webpages and understand how it works.
    (a)  Systems.tf should contain the demo video (problem, context, solution, benefits, trial instructions) and all necessary information to perform this end-to-end user flow.
    (b)  Discourse Terraphim should contain the topic that addresses Q&A for this user flow.
2. Download installation packages for Terraphim desktop and browser extension, Atomic Server, GitHubDesktop, and Logseq from the websites. Check the control sums (optional) and install all of them.
    (a)  Links to installation packages should be available on the downloads page.
    (b)  Readme.txt with installation and setup instructions should be available at terraphim.ai and systems.tf websites.
3. Add a demo graph (INCOSE-Systems-Engineering) or actual domain graph in GitHub Desktop.
    (a) a demo video should explain why and how we use domain graphs, including the technical side.
    (b) Should be user instructions on how to add a demo graph in GitHub Desktop.
4. Open Logseq and add the domain graph from the local folder of the GitHub repository.
    (a)  Should be user instructions on how to add the graph and why the user needs it (short explanation on semantic interoperability).
5. Perform {{query "type:: [[TerraphimRole]]"}} in Logseq and get the list of Terraphim roles available in the graph (domain graph pages). Open the Terraphim role page and export it as JSON to the local folder (MacBook “Downloads”).
    (a) A short tutorial and an article on role mechanisms should be available.
6. Open the Terraphim desktop app and import (drag and drop) the JSON file with the Terraphim role. Select the local domain graph folder for Terraphim Desktop, import the graph, and add it as a local haystack. Export domain graph to a browser extension.
    (a) a short video tutorial on performing Terraphim role export and import should be available, and an explanation of the haystack mechanism.
7. Select a local folder with files (projects, library) as a haystack.
8. Open systems.tf website or working resource and test that the web extension tags the Terraphim role concepts with the command “Ground concepts”. The browser extension shows the counter for concepts on the page, the breakdown, and orphaned/omitted concepts. Possible action: add the webpage to the Terraphim Cortex haystack.
9. Select the type of highlight for the Terraphim role. Ground concepts feature - links to graph pages or backlinks.
10.  Select whether inputs, activities, and outputs will be shown according to the selected Terraphim role for the Ground concepts feature. Format [[Concept: input/output/activity]], for example, [[System concepts: input]].
11.  Search: selecting haystacks - local folder with sources and the Logseq graph.
12.  Search: prompt autocompletion from graph concepts.
13.  Search: results showing the source, metadata (obligatory), and summarization of the paragraph where the search term is found.
14.  Search: open the webpage from the link to the source (only for webpages).
15.  Search: add the webpage to the Terrahim Cortex haystack.
16.  Command “Annotate” from the context menu creates the node in the domain graph. It adds Zotero-like metadata from the webpage and additional property terraphimrole:: [[System operator (or whatever that is selected)]]. The page's name appears in the clipboard so you can find and open it in the Logseq app and the Terraphim role in the Logseq side pane.
17.  On the side pane, three sections with a checklist appear: Do general and specific relationship names make sense? Do narrower terms contradict or match broader terms or put them into question? Is there a cause-effect chain between inputs, activities, and outputs? After each question, there is a blank field for user entry. Notes are connected to a paragraph, and once the annotated section is sent to Logseq (copied to clipboard), you can paste it with all your notes under the title and the front matter.
18.  After the whole article is annotated, a user writes his overall notes and tags synonyms.
AlexMikhalev commented 9 months ago

we don't need github desktop, we also can package local KG - from logseq to serve KG per role locally, without need to go out of desktop. Is it desirable? We can keep systems.tf for examples of how it can be used.

turkhale commented 9 months ago

Yes that is highly desirable.

El El sáb, 18 nov 2023 a las 14:10, Dr Alexander Mikhalev < @.***> escribió:

we don't need github desktop, we also can package local KG - from logseq to serve KG per role locally, without need to go out of desktop. Is it desirable? We can keep systems.tf for examples of how it can be used.

— Reply to this email directly, view it on GitHub https://github.com/terraphim/terraphim-project/issues/25#issuecomment-1817505808, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBJHGDBY6SUMP4YWDTSN6DYFCXVXAVCNFSM6AAAAAA7PPVUX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGUYDKOBQHA . You are receiving this because you authored the thread.Message ID: @.***>