AlMeta:QuiteUnusual:Concept mapping design doc - Revision history

Cmdrtako: Cmdrtako moved page QuiteUnusual:Concept mapping design doc to AlMeta:QuiteUnusual:Concept mapping design doc without leaving a redirect

2022-05-22T02:20:30Z

Cmdrtako moved page QuiteUnusual:Concept mapping design doc to AlMeta:QuiteUnusual:Concept mapping design doc without leaving a redirect

Cmdrtako: Cmdrtako moved page YMO:Concept mapping design doc to QuiteUnusual:Concept mapping design doc without leaving a redirect

2022-05-22T02:10:30Z

Cmdrtako moved page YMO:Concept mapping design doc to QuiteUnusual:Concept mapping design doc without leaving a redirect

Cmdrtako at 04:37, 12 April 2020

2020-04-12T04:37:31Z

Cmdrtako at 22:51, 5 April 2020

2020-04-05T22:51:15Z

Cmdrtako: /* popular article for a node */

2020-04-04T16:01:18Z

‎popular article for a node

Cmdrtako at 16:00, 4 April 2020

2020-04-04T16:00:00Z

Cmdrtako at 14:26, 4 April 2020

2020-04-04T14:26:12Z

Cmdrtako: updated datamodel

2020-04-04T12:56:07Z

updated datamodel

Cmdrtako at 13:07, 3 April 2020

2020-04-03T13:07:01Z

Cmdrtako at 12:11, 2 April 2020

2020-04-02T12:11:57Z

@@ Line 2: / Line 2: @@
 [[File:UIdm.png]]
-Users can selec their version, the version specified in the map/article that they followed to that node, the most popular version(one they are most likely to approve of that they haven't approved, ether directly of through a proxy), or  select a user to see their version.
+== what version of node to show ==
 Should show versions that they are linkly to revise. show under user's menu(at the top of the list)(just use a randum unaprroved version in MVP. the one that has the highest likelyhood of being disaproved(disagree that the aproved tag aplies) of)
@@ Line 111: / Line 123: @@
 == ?successors ==
 Articles what have this article as their "Based on"
-== What links connect to/from them ==
+== ?What links connect to/from them ==
-== users that have approved this node(another tag?)==
+== ?users that have approved this node(another tag?)==
-== users that have made comments and tags ==
+== ?users that have made comments and tags ==
 = Link =
@@ Line 141: / Line 153: @@
 == @after ==
 the last message on this board that the user had when thru posted this message. should be after that message and sorted by time
 == @replying to ==
+== ?replies==
 = Map =
 == @#Nodes ==
-=== @Article ===
+=== @title ===
-the version that they where refering when they made the link
+title of node used in this map
 == @links between them nodes ==
 == ?Layouts for this maps ===
 == @Based off of ==
-Map that this map is based off ot
+Map that this map is based off of.
 = layout =

@@ Line 12: / Line 12: @@
 Pairs of students were put in one of three conditions. In one condition, they were asked to collaboratively construct a diagram, using the following labels for the viewpoint and arguments (boxes): viewpoint, argument in favour, argument against, support, rebuttal, and example. In the second condition, students were asked to collaboratively construct a diagram using the following labels for relations (arrows) between arguments (boxes): because, but, and, thus, such as.
 ----
-= users =
+= tag =
 == recommended display name ==
-== full name ==
+= user =
-== articles ==
+== ?recommended display name ==
-=== comments ===
+== ?full name ==
-=== tags ===
+== ?#Tags==
-Can be agree that the tag aplies unset or disagree's that the tag aplies
+=== Display name ===
 === if they approved the article ====
-Could be just another tag but needs to calculate the likelyhood of them disagreeing that it's aproved not just the likelyhood that it is approved but is that just 1=(approve likelyhood)?
+Could be just another tag but needs to calculate the likelihood of them disagreeing that it's approved not just the likelihood that it is approved but is that just 1=(approve likelihood)?
-=== Nodes that they have edited ===
+== ?#links ==
-=== friends list ===
+=== ?comments ===
-=== ignore list ===
+messages this user has made in link corresponding comment chatroom
 ignore list takes priority over friends list when deciding to show a node to the user
-=== Authorities ===
+== ?Authorities ==
-order list of users. when deciding on which article to show for their version start with ones they approved then go their their authorities list look for one that they approved select the newest one if none of them have approved an article for that node do the same thing to their authorities authoritie list.
+order list of users. when deciding on which article to show for their version start with ones they approved then go their their authorities list look for one that they approved select the newest one if none of them have approved an article for that node do the same thing to their authorities authorities list.
 Example with this graph:
@@ Line 65: / Line 90: @@
-= all objects =
+= Node =
 == ?title ==
 == ?List of articles ==
@@ Line 80: / Line 97: @@
 == ?What links connect to/from them ==
-= articles =
+= article =
 == @title ==
 Title that this article was written for
@@ Line 98: / Line 115: @@
 == users that have made comments and tags ==
-= Links =
+= Link =
 == @Author ==
 == @node1 ==
-=== @Article ===
+== @Article1 ==
-the version that they where referring when they made the link
+the version of node1 that they where referring when they made the link
 == @node2 ==
-=== @Article ===
+== @Article2 ==
-the version that they where referring when they made the link
+the version of node2 that they where referring when they made the link
 == @Type of link ==
 == ?What maps are they in? ==
 == ?Comments ==
-Chatroom to discuss the article
+Chatroom to discuss the link
 ==  ?tags ==
 The tags or link to the users that have put them on it?
@@ Line 126: / Line 143: @@
 == @replying to ==
-= Maps =
+= Map =
-== @Nodes ==
+== @#Nodes ==
 === @Article ===
 the version that they where refering when they made the link
@@ Line 138: / Line 155: @@
 == @map this layout is for ==
 Should be able to apply layouts to different maps. layering them ontop of the current node relations and ignoring relations that refer to nodes that aren't in the map
-== Horizontal orderings ==
+== @#Horizontal orderings ==
 === @node1 ===
 === @node2 ===
 === @Left, overlaping, or right ===
-== @Vertical orderings ==
+== @#Vertical orderings ==
 === @node1 ===
 === @node2 ===
 === @Above,overlaping, below ===
-== @relitive positions ==
+== @#relitive positions ==
   if a node has already been moved by a relative move the one that hasn't else find the center between them and move the nodes reletive to that.
 === @node1 ===
 === @node2 ===
 === @position of node1 reletive to node2 ===

@@ Line 6: / Line 6: @@
 Should show versions that they are linkly to revise. show under user's menu(at the top of the list)(just use a randum unaprroved version in MVP. the one that has the highest likelyhood of being disaproved(disagree that the aproved tag aplies) of)
 ----
-= popular article for a node =

@@ Line 5: / Line 5: @@
 Should show versions that they are linkly to revise. show under user's menu(at the top of the list)(just use a randum unaprroved version in MVP. the one that has the highest likelyhood of being disaproved(disagree that the aproved tag aplies) of)
 = users =
@@ Line 20: / Line 30: @@
 ignore list takes priority over friends list when deciding to show a node to the user
 === Authorities ===
-order list of users. when deciding on which article to show for their version start with ones they approved then go their their authorities list look for one that they approved select the newest one if none of them have approved an article for that node do the same thing to thier authoritie's authoritie list.
+order list of users. when deciding on which article to show for their version start with ones they approved then go their their authorities list look for one that they approved select the newest one if none of them have approved an article for that node do the same thing to their authorities authoritie list.
 Example with this graph:
@@ Line 85: / Line 95: @@
 == @based on ==
 immediate previous version
+== ?successors ==
 == What links connect to/from them ==
 == users that have approved this node(another tag?)==

@@ Line 74: / Line 74: @@
 = articles =
 == @Wikibody ==
 == @Templates ==
@@ Line 92: / Line 94: @@
 == @node1 ==
 === @Article ===
-the version that they where refering when they made the link
+the version that they where referring when they made the link
 == @node2 ==
 === @Article ===
-the version that they where refering when they made the link
+the version that they where referring when they made the link
 == @Type of link ==
 == ?What maps are they in? ==
@@ Line 108: / Line 110: @@
 = Message =
 == ?edits ==
 Only author should be able to add edits.
@@ Line 130: / Line 130: @@
 == @map this layout is for ==
 Should be able to apply layouts to different maps. layering them ontop of the current node relations and ignoring relations that refer to nodes that aren't in the map
-== Horizontal order ==
+== Horizontal orderings ==
 === @node1 ===
 === @node2 ===
 === @Left, overlaping, or right ===
-== @Vertical order ==
+== @Vertical orderings ==
 === @node1 ===
 === @node2 ===
 === @Above,overlaping, below ===
-== @relitive position ==
+== @relitive positions ==
   if a node has already been moved by a relative move the one that hasn't else find the center between them and move the nodes reletive to that.
 === @node1 ===
 === @node2 ===
 === @position of node1 reletive to node2 ===

← Older revision	Revision as of 02:20, 22 May 2022
(No difference)

← Older revision	Revision as of 02:10, 22 May 2022
(No difference)

@@ Line 58: / Line 58: @@
 = Nodes =
-== title ==
+== ?title ==
-== List of articles ==
+== ?List of articles ==
 versions of the node
-== What maps are they in ==
+== ?What maps are they in ==
-== What links connect to/from them ==
+== ?What links connect to/from them ==
 = articles =
-== user that made node(shouldn't)
+== @Wikibody ==
-== Wikibody ==
+== @Templates ==
-=== Templates ===
+== @Update ==
 If set to a user id it should use the current(display time) version of the node that that specified user would see if they went to the linked node.
 If not a user id(false? undefined?) use the specific article linked in the template
 == What links connect to/from them ==
 == users that have approved this node(another tag?)==
@@ Line 82: / Line 89: @@
 = Links =
-== Author ==
+== @Author ==
-== node1 ==
+== @node1 ==
-== node2 ==
+=== @Article ===
-== Type of link ==
+the version that they where refering when they made the link
-== What maps are they in? ==
+== @node2 ==
-== Comments ==
+=== @Article ===
-The comments or link to the users that have put them on it?
+the version that they where refering when they made the link
-==  tags ==
+== @Type of link ==
-The same as comments. The tags or link to the users that have put them on it?
+== ?What maps are they in? ==
 = Maps =
-== Nodes ==
+== @Nodes ==
-=== Article(the version that they where refering when they made the link)
+=== @Article ===
-== links between them nodes ==
+the version that they where refering when they made the link
 = layout =
 == Horizontal order ==
-=== node1 ===
+=== @node1 ===
-=== node2 ===
+=== @node2 ===
-=== Left, overlaping, or right ===
+=== @Left, overlaping, or right ===
-== Vertical order ==
+== @Vertical order ==
-=== node1 ===
+=== @node1 ===
-=== node2 ===
+=== @node2 ===
-=== Above,overlaping, below ===
+=== @Above,overlaping, below ===
-== relitive position ==
+== @relitive position ==
   if a node has already been moved by a relative move the one that hasn't else find the center between them and move the nodes reletive to that.
-=== node1 ===
+=== @node1 ===
-=== node2 ===
+=== @node2 ===
-=== position of node1 reletive to node2 ===
+=== @position of node1 reletive to node2 ===