Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
gargantext
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
humanities
gargantext
Commits
84a9a070
Commit
84a9a070
authored
Jun 21, 2017
by
sim
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'testing' into simon-testing
parents
06b2fb4d
9a6805bf
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
85 additions
and
0 deletions
+85
-0
architecture.md
docs/architecture.md
+82
-0
index.md
docs/index.md
+3
-0
No files found.
docs/architecture.md
0 → 100644
View file @
84a9a070
# Definitions and notation for the documentation (!= python notation)
## Node
The table (nodes) is a list of nodes:
[
Node
]
Each Node has:
-
a typename
-
a parent_id
-
a name
### Each Node has a parent_id
Node A
├── Node B
└── Node C
If Node A is Parent of Node B and Node C
then NodeA.id == NodeB.parent_id == NodeC.parent_id.
### Each Node has a typename
Notation: Node
[
foo
](
bar
)
is a Node of typename "foo" and with name "bar".
Then:
-
Then Node
[
project
]
is a project.
-
Then Node
[
corpus
]
is a corpus.
-
Then Node
[
document
]
is a document.
### Each Node as a typename and a parent
Node
[
user
](
name
)
├── Node
[
project
](
myProject1
)
│ ├── Node
[
corpus
](
myCorpus1
)
│ ├── Node
[
corpus
](
myCorpus2
)
│ └── Node
[
corpus
](
myCorpus3
)
└── Node
[
project
](
myProject2
)
/!
\
3 way to manage rights of the Node:
1) Then Node
[
User
]
is a folder containing all User projects and corpus and
documents (i.e. Node
[
user
]
is the parent_id of the children).
2) Each node as a user_id (mainly used today)
3) Right management for the groups (implemented already but not
used since not connected to the frontend).
## Global Parameters
Global User is Gargantua (Node with typename User).
This node is the parent of the others Nodes for parameters.
Node
[
user
](
gargantua
)
(
gargantua.id
== Node
[
user
]
.user_id)
├── Node
[
TFIDF-Global
](
global
)
: without group
│ ├── Node
[
tfidf
](
database1
)
│ ├── Node
[
tfidf
](
database2
)
│ └── Node
[
tfidf
](
database2
)
└── Node
[
anotherMetric
](
global
)
## NodeNgram
NodeNgram is a relation of a Node with a ngram:
-
document and ngrams
-
metrics and ngrams (position of the node metrics indicates the
context)
# Community Parameters
# User Parameters
docs/index.md
View file @
84a9a070
...
...
@@ -8,6 +8,9 @@ Gargantext is a web plateform to explore your corpora using text-mining[...](abo
*
[
Take a tour
](
demo.md
)
of the different features offered by Gargantext
## Architecture
*
[
Architecture
](
architecture.md
)
Architecture of Gargantext
##Need some help?
Ask the community at:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment