Difference between revisions of "AlMeta:QuiteUnusual:Concept mapping design doc"
(updated datamodel) |
|||
| Line 58: | Line 58: | ||
| + | = all objects = | ||
| + | A property that Starts with @ is static. A node that starts with ? can be add to. | ||
| + | |||
| + | == @author == | ||
| + | user that made node | ||
| + | == @Timestamp == | ||
| + | Time when the object is reportedly created | ||
= Nodes = | = Nodes = | ||
| − | == title == | + | == ?title == |
| − | == List of articles == | + | == ?List of articles == |
versions of the node | 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 = | = articles = | ||
| − | == | + | == @Wikibody == |
| − | + | == @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 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 | If not a user id(false? undefined?) use the specific article linked in the template | ||
| + | == ?Nodes and Messages that link to this article == | ||
| + | == @based on == | ||
| + | immediate previous version | ||
| − | |||
| − | |||
| − | |||
== 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?)== | ||
| Line 82: | Line 89: | ||
= Links = | = 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 version that they where refering when they made the link | |
| − | == tags == | + | == @Type of link == |
| − | + | == ?What maps are they in? == | |
| + | == ?Comments == | ||
| + | Chatroom to discuss the article | ||
| + | == ?tags == | ||
| + | The tags or link to the users that have put them on it? | ||
| + | |||
| + | = Chatroom/board = | ||
| + | == ?Messages == | ||
| + | list of messages on this board | ||
| + | |||
| + | = Message = | ||
| + | == @title == | ||
| + | == @author == | ||
| + | == ?edits == | ||
| + | Only author should be able to add edits. | ||
| + | the article that makes up the body of the message. list of all the edits | ||
| + | == @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 == | ||
| + | |||
= Maps = | = Maps = | ||
| − | == Nodes == | + | == @Nodes == |
| − | === Article | + | === @Article === |
| − | == links between them nodes == | + | the version that they where refering when they made the link |
| + | == @links between them nodes == | ||
| + | == ?Layouts for this maps === | ||
| + | == @Based off of == | ||
| + | Map that this map is based off ot | ||
= layout = | = layout = | ||
| + | == @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 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. | 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 === |
Revision as of 14:56, 4 April 2020
This is for the AntiWikipedia side. for the game side see:YMO_Prototype_Design_Doc
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.
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)
Contents
users
recommended display name
full name
articles
comments
tags
Can be agree that the tag aplies unset or disagree's that the tag aplies
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)?
Nodes that they have edited
friends list
ignore list
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.
Example with this graph:
- a
- b
- c
- d
- b
- e
- f
- d
- c
- x
- y
- z
- d
- e
- q
- r
- s
- for a get a's, b's, c's and d's aproves articles for the node, if it not empty selevt the newest one.
- if it is empty get b's authlist's( e's, f's and d's) approved articles for the node, if it not empty select the newest one.
- if it is empty get c's authlist's( x's, y's and z's) approved articles for the node, if it not empty select the newest one.
- if it is empty get d's authlist's approved articles for the node, since it's empty get e's authlist's (q's, r's, s's) approved articles for the node, if it not empty select the newest one.
- if it's empty get f's dauthlist's approved articles for the node, if it not empty select the newest one.
- if it's empty get d's authlist's approved articles for the node, it's empty so get x's authlist's apprived articles for the node, if it not empty select the newest one.
- if it's empty get y's authlist's approved articles for the node, if it not empty select the newest one.
- if it's empty get z's authlist's approved articles for the node, if it not empty select the newest one.
- if it's empty get q's authlist's approved articles for the node, if it not empty select the newest one.
- if it's empty get r's authlist's approved articles for the node, if it not empty select the newest one.
- if it's empty get s's authlist's approved articles for the node, if it not empty select the newest one.
- continue crawling the web of authority with the the first of q's authlist. continue through q's authlist
- continue crawling the web of authority with the the first of r's authlist. continue through r's authlist
- continue crawling the web of authority with the the first of s's authlist. continue through s's authlist
all objects
A property that Starts with @ is static. A node that starts with ? can be add to.
@author
user that made node
@Timestamp
Time when the object is reportedly created
Nodes
?title
?List of articles
versions of the node
?What maps are they in
?What links connect to/from them
articles
@Wikibody
@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
?Nodes and Messages that link to this article
@based on
immediate previous version
What links connect to/from them
users that have approved this node(another tag?)
users that have made comments and tags
Links
@Author
@node1
@Article
the version that they where refering when they made the link
@node2
@Article
the version that they where refering when they made the link
@Type of link
?What maps are they in?
?Comments
Chatroom to discuss the article
?tags
The tags or link to the users that have put them on it?
Chatroom/board
?Messages
list of messages on this board
Message
@title
@author
?edits
Only author should be able to add edits.
the article that makes up the body of the message. list of all the edits
@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
Maps
@Nodes
@Article
the version that they where refering when they made the link
@links between them nodes
?Layouts for this maps =
@Based off of
Map that this map is based off ot
layout
@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
@node1
@node2
@Left, overlaping, or right
@Vertical order
@node1
@node2
@Above,overlaping, below
@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.
