Commit adc03f7e authored by Sebastian's avatar Sebastian

erp5_osoe_theory_data: improvements by ni and jp to prepare for coursera course

parent 745f70e1
......@@ -85,10 +85,11 @@
<key> <string>categories</string> </key>
<value>
<tuple>
<string>contributor/person_module/20150701-47AE54D</string>
<string>publication_section/documentation/user</string>
<string>classification/collaborative/team</string>
<string>group/nexedi</string>
<string>contributor/person_module/20150701-47AE54D</string>
<string>contributor/person_module/2326</string>
</tuple>
</value>
</item>
......@@ -281,7 +282,7 @@
</item>
<item>
<key> <string>actor</string> </key>
<value> <string>superklaus</string> </value>
<value> <string>klaus.woelfel</string> </value>
</item>
<item>
<key> <string>comment</string> </key>
......@@ -295,7 +296,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.32902.63370.29138</string> </value>
<value> <string>952.33148.54636.39504</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -313,7 +314,7 @@
</tuple>
<state>
<tuple>
<float>1468333245.79</float>
<float>1469112194.44</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -85,10 +85,11 @@
<key> <string>categories</string> </key>
<value>
<tuple>
<string>contributor/person_module/20150701-47AE54D</string>
<string>publication_section/documentation/user</string>
<string>classification/collaborative/team</string>
<string>group/nexedi</string>
<string>contributor/person_module/20150701-47AE54D</string>
<string>contributor/person_module/2326</string>
</tuple>
</value>
</item>
......@@ -281,7 +282,7 @@
</item>
<item>
<key> <string>actor</string> </key>
<value> <string>superklaus</string> </value>
<value> <string>klaus.woelfel</string> </value>
</item>
<item>
<key> <string>comment</string> </key>
......@@ -295,7 +296,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.32902.63370.29138</string> </value>
<value> <string>952.46130.55665.14971</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -313,7 +314,7 @@
</tuple>
<state>
<tuple>
<float>1468333204.07</float>
<float>1469112235.26</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -316,7 +316,7 @@
</tuple>
<state>
<tuple>
<float>1468329020.86</float>
<float>1471851320.56</float>
<string>UTC</string>
</tuple>
</state>
......
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- Created with Inkscape (http://www.inkscape.org/) -->
<svg
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
width="1052.3622"
height="744.09448"
id="svg3359"
version="1.1"
inkscape:version="0.48.3.1 r9886"
sodipodi:docname="Neues Dokument 1">
<defs
id="defs3361">
<marker
inkscape:stockid="Arrow2Lstart"
orient="auto"
refY="0"
refX="0"
id="Arrow2Lstart-9"
style="overflow:visible">
<path
id="path6481-4"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(1.1,0,0,1.1,1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lstart"
orient="auto"
refY="0"
refX="0"
id="marker3659"
style="overflow:visible">
<path
id="path3661"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(1.1,0,0,1.1,1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lend"
orient="auto"
refY="0"
refX="0"
id="Arrow2Lend-79"
style="overflow:visible">
<path
id="path6484-6"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lstart"
orient="auto"
refY="0"
refX="0"
id="marker3665"
style="overflow:visible">
<path
id="path3667"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(1.1,0,0,1.1,1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lend"
orient="auto"
refY="0"
refX="0"
id="marker3669"
style="overflow:visible">
<path
id="path3671"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<linearGradient
y2="517.06073"
x2="449.7724"
y1="486.81754"
x1="450.91852"
gradientTransform="matrix(2.2290492,0,0,1.5312,-60.240394,-59.750921)"
gradientUnits="userSpaceOnUse"
id="linearGradient4481"
xlink:href="#linearGradient3842-7-1"
inkscape:collect="always" />
<linearGradient
inkscape:collect="always"
id="linearGradient3842-7-1">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844-8-0" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846-2-4" />
</linearGradient>
<linearGradient
y2="517.06073"
x2="449.7724"
y1="486.81754"
x1="450.91852"
gradientTransform="matrix(2.2290492,0,0,1.5312,-298.97382,58.177658)"
gradientUnits="userSpaceOnUse"
id="linearGradient4441"
xlink:href="#linearGradient3842-1-6-8"
inkscape:collect="always" />
<linearGradient
inkscape:collect="always"
id="linearGradient3842-1-6-8">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844-03-2-2" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846-78-8-9" />
</linearGradient>
<linearGradient
inkscape:collect="always"
id="linearGradient3842-1-6">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844-03-2" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846-78-8" />
</linearGradient>
<marker
inkscape:stockid="Arrow2Lstart"
orient="auto"
refY="0"
refX="0"
id="marker3685"
style="overflow:visible">
<path
id="path3687"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(1.1,0,0,1.1,1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lstart"
orient="auto"
refY="0"
refX="0"
id="marker3689"
style="overflow:visible">
<path
id="path3691"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(1.1,0,0,1.1,1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lend"
orient="auto"
refY="0"
refX="0"
id="Arrow2Lend"
style="overflow:visible">
<path
id="path6484"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lend"
orient="auto"
refY="0"
refX="0"
id="marker3695"
style="overflow:visible">
<path
id="path3697"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lend"
orient="auto"
refY="0"
refX="0"
id="marker3699"
style="overflow:visible">
<path
id="path3701"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lend"
orient="auto"
refY="0"
refX="0"
id="marker3703"
style="overflow:visible">
<path
id="path3705"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(-1.1,0,0,-1.1,-1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<marker
inkscape:stockid="Arrow2Lstart"
orient="auto"
refY="0"
refX="0"
id="marker3707"
style="overflow:visible">
<path
id="path3709"
style="font-size:12px;fill-rule:evenodd;stroke-width:0.625;stroke-linejoin:round"
d="M 8.7185878,4.0337352 -2.2072895,0.01601326 8.7185884,-4.0017078 c -1.7454984,2.3720609 -1.7354408,5.6174519 -6e-7,8.035443 z"
transform="matrix(1.1,0,0,1.1,1.1,0)"
inkscape:connector-curvature="0" />
</marker>
<linearGradient
inkscape:collect="always"
xlink:href="#linearGradient3842"
id="linearGradient3379"
gradientUnits="userSpaceOnUse"
gradientTransform="matrix(2.2290492,0,0,1.5312,-267.33445,-333.00003)"
x1="450.91852"
y1="486.81754"
x2="449.7724"
y2="517.06073" />
<linearGradient
inkscape:collect="always"
id="linearGradient3842">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846" />
</linearGradient>
<linearGradient
inkscape:collect="always"
id="linearGradient3842-9">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844-4" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846-5" />
</linearGradient>
<linearGradient
y2="517.06073"
x2="449.7724"
y1="486.81754"
x1="450.91852"
gradientTransform="matrix(2.2290492,0,0,1.5312,-65.993044,-171.92689)"
gradientUnits="userSpaceOnUse"
id="linearGradient3326-5"
xlink:href="#linearGradient3842-7"
inkscape:collect="always" />
<linearGradient
inkscape:collect="always"
id="linearGradient3842-7">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844-8" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846-2" />
</linearGradient>
<linearGradient
y2="517.06073"
x2="449.7724"
y1="486.81754"
x1="450.91852"
gradientTransform="matrix(4.3285183,0,0,1.5312,-1503.0588,-65.46061)"
gradientUnits="userSpaceOnUse"
id="linearGradient3326-6"
xlink:href="#linearGradient3842-6"
inkscape:collect="always" />
<linearGradient
inkscape:collect="always"
id="linearGradient3842-6">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844-6" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846-4" />
</linearGradient>
<linearGradient
y2="517.06073"
x2="449.7724"
y1="486.81754"
x1="450.91852"
gradientTransform="matrix(2.2290492,0,0,1.5312,-575.09923,58.220583)"
gradientUnits="userSpaceOnUse"
id="linearGradient3326-0"
xlink:href="#linearGradient3842-96"
inkscape:collect="always" />
<linearGradient
inkscape:collect="always"
id="linearGradient3842-96">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844-0" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846-7" />
</linearGradient>
<linearGradient
y2="517.06073"
x2="449.7724"
y1="486.81754"
x1="450.91852"
gradientTransform="matrix(0.76922548,0,0,0.5284038,-153.0328,29.501265)"
gradientUnits="userSpaceOnUse"
id="linearGradient3326-8"
xlink:href="#linearGradient3842-1"
inkscape:collect="always" />
<linearGradient
inkscape:collect="always"
id="linearGradient3842-1">
<stop
style="stop-color:#fdfc7c;stop-opacity:1;"
offset="0"
id="stop3844-03" />
<stop
style="stop-color:#fdfc7c;stop-opacity:0;"
offset="1"
id="stop3846-78" />
</linearGradient>
<linearGradient
y2="517.06073"
x2="449.7724"
y1="486.81754"
x1="450.91852"
gradientTransform="matrix(2.2290492,0,0,1.5312,-705.52098,184.82103)"
gradientUnits="userSpaceOnUse"
id="linearGradient3783"
xlink:href="#linearGradient3842-1"
inkscape:collect="always" />
<linearGradient
inkscape:collect="always"
xlink:href="#linearGradient3842-9"
id="linearGradient4008"
gradientUnits="userSpaceOnUse"
gradientTransform="matrix(2.2290492,0,0,1.5312,-575.09923,-177.67948)"
x1="450.91852"
y1="486.81754"
x2="449.7724"
y2="517.06073" />
<linearGradient
inkscape:collect="always"
xlink:href="#linearGradient3842-1-6"
id="linearGradient4010"
gradientUnits="userSpaceOnUse"
gradientTransform="matrix(2.2290492,0,0,1.5312,-445.57953,184.7351)"
x1="450.91852"
y1="486.81754"
x2="449.7724"
y2="517.06073" />
</defs>
<sodipodi:namedview
id="base"
pagecolor="#ffffff"
bordercolor="#666666"
borderopacity="1.0"
inkscape:pageopacity="0.0"
inkscape:pageshadow="2"
inkscape:zoom="0.35"
inkscape:cx="30.473726"
inkscape:cy="515.5909"
inkscape:document-units="px"
inkscape:current-layer="layer1"
showgrid="false"
inkscape:window-width="1366"
inkscape:window-height="721"
inkscape:window-x="-2"
inkscape:window-y="-3"
inkscape:window-maximized="1" />
<metadata
id="metadata3364">
<rdf:RDF>
<cc:Work
rdf:about="">
<dc:format>image/svg+xml</dc:format>
<dc:type
rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
<dc:title></dc:title>
</cc:Work>
</rdf:RDF>
</metadata>
<g
inkscape:label="Ebene 1"
inkscape:groupmode="layer"
id="layer1"
transform="translate(0,-308.2677)">
<rect
style="fill:url(#linearGradient3783);fill-opacity:1;stroke:#000000;stroke-width:2.37657523;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9-6"
width="208.05403"
height="52.3092"
x="190.92354"
y="924.14838"
ry="17.301088" />
<rect
style="fill:url(#linearGradient3326-0);fill-opacity:1;stroke:#000000;stroke-width:2.37657523;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9-1"
width="208.05403"
height="52.3092"
x="321.34521"
y="797.54791"
ry="17.301088" />
<rect
style="fill:url(#linearGradient3326-6);fill-opacity:1;stroke:#000000;stroke-width:2.37618303;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9-2"
width="404.0134"
height="52.3092"
x="237.71751"
y="673.86676"
ry="17.301088" />
<rect
style="fill:url(#linearGradient3326-5);fill-opacity:1;stroke:#000000;stroke-width:2.37657523;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9-3"
width="208.05403"
height="52.3092"
x="830.45135"
y="567.40051"
ry="17.301088" />
<rect
style="fill:url(#linearGradient4008);fill-opacity:1;stroke:#000000;stroke-width:2.37657523;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9-9"
width="208.05403"
height="52.3092"
x="321.34521"
y="561.64789"
ry="17.301088" />
<rect
style="fill:url(#linearGradient3379);fill-opacity:1;stroke:#000000;stroke-width:2.37657523;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9"
width="208.05403"
height="52.3092"
x="629.10992"
y="406.32742"
ry="17.301088" />
<path
sodipodi:type="arc"
style="fill:#d41d19;fill-opacity:1;stroke:#000000;stroke-width:1;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="path11099"
sodipodi:cx="437.72925"
sodipodi:cy="60.674309"
sodipodi:rx="5.83639"
sodipodi:ry="6.897552"
d="m 443.56564,60.674309 a 5.83639,6.897552 0 1 1 -11.67278,0 5.83639,6.897552 0 1 1 11.67278,0 z"
transform="matrix(2.1711629,0,0,1.5908465,-527.36913,342.29107)" />
<path
style="fill:none;stroke:#000000;stroke-width:1.85849047;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-9);marker-end:none"
d="M 690.22455,462.29616 540.48649,592.82011"
id="path11109"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:1.85849047px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;marker-start:none;marker-end:url(#Arrow2Lend)"
d="m 423.89881,449.78752 0,106.35313"
id="path11111"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:1.60281229;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:none;marker-end:url(#Arrow2Lend)"
d="m 424.12456,618.19161 0,49.92246"
id="path11111-1"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:1.85849047;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:none;marker-end:url(#Arrow2Lend)"
d="m 424.12615,725.0309 0,68.29787"
id="path11111-1-5"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:2.12773919;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:none;marker-end:url(#Arrow2Lend)"
d="m 406.04979,859.0178 -54.45977,55.46756"
id="path11111-1-5-6"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:2.32167029;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-9);marker-end:none"
d="M 827.84872,704.3896 649.47157,701.48707"
id="path11109-3"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:2.16120386;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-9);marker-end:none"
d="m 804.70557,600.02106 -152.68106,99.2567"
id="path11109-1"
inkscape:connector-curvature="0" />
<image
y="391.54828"
x="108.98876"
id="image4476"
height="112.00775"
width="144.2462"
xlink:href="http://www.erp5.com/P-OSOE-Ticket.Icone.Man.1?format=png" />
<image
y="686.83148"
x="12.010618"
id="image4612"
height="110.42873"
width="148.55632"
xlink:href="http://www.erp5.com/P-OSOE-Ticket.Icone.Woman.2?format=png" />
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="678.48718"
y="441.11093"
id="text3466"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3468"
x="678.48718"
y="441.11093">deleted</tspan></text>
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="868.32343"
y="602.18396"
id="text3470"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3472"
x="868.32343"
y="602.18396">cancelled</tspan></text>
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="359.00244"
y="596.47437"
id="text3474"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3476"
x="359.00244"
y="596.47437">submitted</tspan></text>
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="304.56744"
y="708.65033"
id="text3478"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3480"
x="304.56744"
y="708.65033">prospect contacted</tspan></text>
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="370.72232"
y="829.41217"
id="text3482"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3484"
x="370.72232"
y="829.41217">offered</tspan></text>
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="266.31635"
y="958.84613"
id="text3486"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3488"
x="266.31635"
y="958.84613">sold</tspan></text>
<text
xml:space="preserve"
style="font-size:38.74087524px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#008080;fill-opacity:1;stroke:none;font-family:Sans"
x="457.73831"
y="495.75931"
id="text6242"
sodipodi:linespacing="125%"
transform="scale(0.98712911,1.0130387)"><tspan
sodipodi:role="line"
id="tspan6244"
x="457.73831"
y="495.75931"
style="font-size:39.96044159px">Draft</tspan></text>
<text
xml:space="preserve"
style="font-size:38.74087524px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#008080;fill-opacity:1;stroke:none;font-family:Sans"
x="105.16744"
y="541.18799"
id="text6242-5"
sodipodi:linespacing="125%"
transform="scale(0.98712911,1.0130387)"><tspan
sodipodi:role="line"
id="tspan6244-6"
x="105.16744"
y="541.18799"
style="font-size:39.96044159px">Prepare</tspan></text>
<text
xml:space="preserve"
style="font-size:38.74087524px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#008080;fill-opacity:1;stroke:none;font-family:Sans"
x="6.0978899"
y="836.47375"
id="text6242-4"
sodipodi:linespacing="125%"
transform="scale(0.98712911,1.0130387)"><tspan
sodipodi:role="line"
id="tspan6244-63"
x="6.0978899"
y="836.47375"
style="font-size:39.96044159px">Manage</tspan></text>
<rect
style="fill:url(#linearGradient4010);fill-opacity:1;stroke:#000000;stroke-width:2.37657523;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9-6-4"
width="208.05403"
height="52.3092"
x="450.86505"
y="924.06244"
ry="17.301088" />
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="503.07556"
y="958.76007"
id="text3486-7"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3488-2"
x="503.07556"
y="958.76007">rejected</tspan></text>
<rect
style="fill:url(#linearGradient4441);fill-opacity:1;stroke:#000000;stroke-width:2.37657523;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9-6-4-9"
width="208.05403"
height="52.3092"
x="597.47058"
y="797.50507"
ry="17.301088" />
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="649.68127"
y="832.20258"
id="text3486-7-6"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3488-2-0"
x="649.68127"
y="832.20258">inruired</tspan></text>
<rect
style="fill:url(#linearGradient4481);fill-opacity:1;stroke:#000000;stroke-width:2.37657523;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none"
id="rect3961-9-3-2"
width="208.05403"
height="52.3092"
x="836.20422"
y="679.57642"
ry="17.301088" />
<text
xml:space="preserve"
style="font-size:27.45360565px;font-style:normal;font-weight:normal;line-height:0%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
x="891.46289"
y="714.36005"
id="text3470-2"
sodipodi:linespacing="0%"><tspan
sodipodi:role="line"
id="tspan3472-2"
x="891.46289"
y="714.36005">expired</tspan></text>
<path
style="fill:none;stroke:#000000;stroke-width:2.28672504;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:none;marker-end:url(#Arrow2Lend-79)"
d="m 437.99608,855.91845 57.23108,60.96422"
id="path11111-1-5-6-0"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:1.98161817;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-9);marker-end:none"
d="M 808.42083,595.0987 540.9568,591.00724"
id="path11109-3-6"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:2.08965516;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:none;marker-end:url(#Arrow2Lend-79)"
d="M 488.83259,908.39631 434.38812,854.88154"
id="path11111-1-5-6-0-4"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:2.19348431;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-9);marker-end:none"
d="m 592.70775,824.60853 -57.43409,0.19908"
id="path11109-3-7"
inkscape:connector-curvature="0" />
<path
style="fill:none;stroke:#000000;stroke-width:1.98291862;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1;stroke-dasharray:none;marker-start:url(#Arrow2Lstart-9);marker-end:none"
d="m 536.6307,823.61699 46.93627,0.19907"
id="path11109-3-7-3"
inkscape:connector-curvature="0" />
</g>
</svg>
<svg width="1052.3622" height="744.09448" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<defs>
<marker orient="auto" refY="0" refX="0" id="Arrow2Lstart-9">
<path id="path6481-4" d="m10.69045,4.43711l-12.01847,-4.4195l12.01847,-4.41949c-1.92005,2.60927 -1.90898,6.1792 0,8.839l0,-0.00001z" stroke-linejoin="round" stroke-width="0.625" fill-rule="evenodd"/>
</marker>
<marker orient="auto" refY="0" refX="0" id="Arrow2Lend-79">
<path id="path6484-6" d="m-10.69045,-4.43711l12.01847,4.4195l-12.01847,4.41949c1.92005,-2.60927 1.90898,-6.1792 0,-8.839l0,0.00001z" stroke-linejoin="round" stroke-width="0.625" fill-rule="evenodd"/>
</marker>
<marker orient="auto" refY="0" refX="0" id="Arrow2Lend">
<path id="path6484" d="m-10.69045,-4.43711l12.01847,4.4195l-12.01847,4.41949c1.92005,-2.60927 1.90898,-6.1792 0,-8.839l0,0.00001z" stroke-linejoin="round" stroke-width="0.625" fill-rule="evenodd"/>
</marker>
<linearGradient y2="1.00166" x2="0.51006" y1="0.11638" x1="0.52234" id="linearGradient4481" xlink:href="#linearGradient3842-7-1"/>
<linearGradient id="linearGradient3842-7-1">
<stop offset="0" id="stop3844-8-0" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846-2-4" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient y2="1.00166" x2="0.51006" y1="0.11638" x1="0.52234" id="linearGradient4441" xlink:href="#linearGradient3842-1-6-8"/>
<linearGradient id="linearGradient3842-1-6-8">
<stop offset="0" id="stop3844-03-2-2" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846-78-8-9" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient id="linearGradient3842-1-6">
<stop offset="0" id="stop3844-03-2" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846-78-8" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient xlink:href="#linearGradient3842" id="linearGradient3379" x1="0.52234" y1="0.11638" x2="0.51006" y2="1.00166"/>
<linearGradient id="linearGradient3842">
<stop offset="0" id="stop3844" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient id="linearGradient3842-9">
<stop offset="0" id="stop3844-4" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846-5" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient y2="1.00166" x2="0.51006" y1="0.11638" x1="0.52234" id="linearGradient3326-5" xlink:href="#linearGradient3842-7"/>
<linearGradient id="linearGradient3842-7">
<stop offset="0" id="stop3844-8" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846-2" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient y2="1.00166" x2="0.51006" y1="0.11638" x1="0.52234" id="linearGradient3326-6" xlink:href="#linearGradient3842-6"/>
<linearGradient id="linearGradient3842-6">
<stop offset="0" id="stop3844-6" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846-4" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient y2="1.00166" x2="0.51006" y1="0.11638" x1="0.52234" id="linearGradient3326-0" xlink:href="#linearGradient3842-96"/>
<linearGradient id="linearGradient3842-96">
<stop offset="0" id="stop3844-0" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846-7" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient id="linearGradient3842-1">
<stop offset="0" id="stop3844-03" stop-color="#fdfc7c"/>
<stop offset="1" id="stop3846-78" stop-opacity="0" stop-color="#fdfc7c"/>
</linearGradient>
<linearGradient y2="1.00166" x2="0.51006" y1="0.11638" x1="0.52234" id="linearGradient3783" xlink:href="#linearGradient3842-1"/>
<linearGradient xlink:href="#linearGradient3842-9" id="linearGradient4008" x1="0.52234" y1="0.11638" x2="0.51006" y2="1.00166"/>
<linearGradient xlink:href="#linearGradient3842-1-6" id="linearGradient4010" x1="0.52234" y1="0.11638" x2="0.51006" y2="1.00166"/>
</defs>
<metadata id="metadata3364">image/svg+xml</metadata>
<g>
<title>background</title>
<rect x="-1" y="-1" width="1054.3622" height="746.09448" id="canvas_background" fill="none"/>
</g>
<g>
<title>Layer 1</title>
<g id="layer1">
<rect id="rect3961-9-6" width="208.05403" height="52.3092" x="190.92354" y="615.88068" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37658" stroke="#000000" fill="url(#linearGradient3783)"/>
<rect id="rect3961-9-1" width="208.05403" height="52.3092" x="321.34521" y="489.28021" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37658" stroke="#000000" fill="url(#linearGradient3326-0)"/>
<rect id="rect3961-9-2" width="404.0134" height="52.3092" x="237.71751" y="365.59906" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37618" stroke="#000000" fill="url(#linearGradient3326-6)"/>
<rect id="rect3961-9-3" width="208.05403" height="52.3092" x="830.45135" y="259.13281" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37658" stroke="#000000" fill="url(#linearGradient3326-5)"/>
<rect id="rect3961-9-9" width="208.05403" height="52.3092" x="321.34521" y="253.38019" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37658" stroke="#000000" fill="url(#linearGradient4008)"/>
<rect id="rect3961-9" width="208.05403" height="52.3092" x="629.10992" y="98.05972" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37658" stroke="#000000" fill="url(#linearGradient3379)"/>
<path id="path11099" d="m435.68413,130.54688a12.67175,10.97294 0 1 1 -25.34351,0a12.67175,10.97294 0 1 1 25.34351,0z" stroke-miterlimit="4" stroke="#000000" fill="#d41d19"/>
<path d="m690.22455,154.02846l-149.73806,130.52395" id="path11109" marker-end="none" marker-start="url(#Arrow2Lstart-9)" stroke-miterlimit="4" stroke-width="1.85849" stroke="#000000" fill="none"/>
<path d="m423.89881,141.51982l0,106.35313" id="path11111" marker-end="url(#Arrow2Lend)" marker-start="none" stroke-width="1.85849px" stroke="#000000" fill="none"/>
<path d="m424.12456,309.92391l0,49.92246" id="path11111-1" marker-end="url(#Arrow2Lend)" marker-start="none" stroke-miterlimit="4" stroke-width="1.60281" stroke="#000000" fill="none"/>
<path d="m424.12615,416.7632l0,68.29787" id="path11111-1-5" marker-end="url(#Arrow2Lend)" marker-start="none" stroke-miterlimit="4" stroke-width="1.85849" stroke="#000000" fill="none"/>
<path d="m406.04979,550.7501l-54.45977,55.46756" id="path11111-1-5-6" marker-end="url(#Arrow2Lend)" marker-start="none" stroke-miterlimit="4" stroke-width="2.12774" stroke="#000000" fill="none"/>
<path d="m827.84872,396.1219l-178.37715,-2.90253" id="path11109-3" marker-end="none" marker-start="url(#Arrow2Lstart-9)" stroke-miterlimit="4" stroke-width="2.32167" stroke="#000000" fill="none"/>
<path d="m804.70557,291.75336l-152.68106,99.2567" id="path11109-1" marker-end="none" marker-start="url(#Arrow2Lstart-9)" stroke-miterlimit="4" stroke-width="2.1612" stroke="#000000" fill="none"/>
<image y="83.28058" x="108.98876" id="image4476" height="112.00775" width="144.2462" xlink:href="http://www.erp5.com/P-OSOE-Ticket.Icone.Man.1?format=png"/>
<image y="378.56378" x="12.01062" id="image4612" height="110.42873" width="148.55632" xlink:href="http://www.erp5.com/P-OSOE-Ticket.Icone.Woman.2?format=png"/>
<text xml:space="preserve" x="678.48718" y="132.84323" id="text3466" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3468" x="678.48718" y="132.84323">deleted</tspan>
</text>
<text xml:space="preserve" x="868.32343" y="293.91626" id="text3470" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3472" x="868.32343" y="293.91626">cancelled</tspan>
</text>
<text xml:space="preserve" x="359.00244" y="288.20667" id="text3474" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3476" x="359.00244" y="288.20667">submitted</tspan>
</text>
<text xml:space="preserve" x="304.56744" y="400.38263" id="text3478" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3480" x="304.56744" y="400.38263">prospect contacted</tspan>
</text>
<text xml:space="preserve" x="370.72232" y="521.14447" id="text3482" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3484" x="370.72232" y="521.14447">offered</tspan>
</text>
<text xml:space="preserve" x="266.31635" y="650.57843" id="text3486" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3488" x="266.31635" y="650.57843">sold</tspan>
</text>
<text xml:space="preserve" x="457.73831" y="495.75931" id="text6242" transform="translate(0,-308.2677001953125) scale(0.9871290922164917,1.0130387544631958) " font-family="Sans" fill="#008080" font-weight="normal" font-style="normal" font-size="38.74088px">
<tspan id="tspan6244" x="457.73831" y="495.75931" font-size="39.96044px">Draft</tspan>
</text>
<text xml:space="preserve" x="105.16744" y="541.18799" id="text6242-5" transform="translate(0,-308.2677001953125) scale(0.9871290922164917,1.0130387544631958) " font-family="Sans" fill="#008080" font-weight="normal" font-style="normal" font-size="38.74088px">
<tspan id="tspan6244-6" x="105.16744" y="541.18799" font-size="39.96044px">Prepare</tspan>
</text>
<text xml:space="preserve" x="6.09789" y="836.47375" id="text6242-4" transform="translate(0,-308.2677001953125) scale(0.9871290922164917,1.0130387544631958) " font-family="Sans" fill="#008080" font-weight="normal" font-style="normal" font-size="38.74088px">
<tspan id="tspan6244-63" x="6.09789" y="836.47375" font-size="39.96044px">Manage</tspan>
</text>
<rect id="rect3961-9-6-4" width="208.05403" height="52.3092" x="450.86505" y="615.79474" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37658" stroke="#000000" fill="url(#linearGradient4010)"/>
<text xml:space="preserve" x="503.07556" y="650.49237" id="text3486-7" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3488-2" x="503.07556" y="650.49237">rejected</tspan>
</text>
<rect id="rect3961-9-6-4-9" width="208.05403" height="52.3092" x="597.47058" y="489.23737" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37658" stroke="#000000" fill="url(#linearGradient4441)"/>
<text xml:space="preserve" x="649.68127" y="523.93488" id="text3486-7-6" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3488-2-0" x="649.68127" y="523.93488">inquired</tspan>
</text>
<rect id="rect3961-9-3-2" width="208.05403" height="52.3092" x="836.20422" y="371.30872" ry="17.30109" stroke-miterlimit="4" stroke-width="2.37658" stroke="#000000" fill="url(#linearGradient4481)"/>
<text xml:space="preserve" x="891.46289" y="406.09235" id="text3470-2" font-family="Sans" fill="#000000" font-weight="normal" font-style="normal" font-size="27.45361px">
<tspan id="tspan3472-2" x="891.46289" y="406.09235">expired</tspan>
</text>
<path d="m437.99608,547.65075l57.23108,60.96422" id="path11111-1-5-6-0" marker-end="url(#Arrow2Lend-79)" marker-start="none" stroke-miterlimit="4" stroke-width="2.28673" stroke="#000000" fill="none"/>
<path d="m808.42083,286.831l-267.46403,-4.09146" id="path11109-3-6" marker-end="none" marker-start="url(#Arrow2Lstart-9)" stroke-miterlimit="4" stroke-width="1.98162" stroke="#000000" fill="none"/>
<path d="m488.83259,600.12861l-54.44447,-53.51477" id="path11111-1-5-6-0-4" marker-end="url(#Arrow2Lend-79)" marker-start="none" stroke-miterlimit="4" stroke-width="2.08966" stroke="#000000" fill="none"/>
<path d="m592.70775,516.34083l-57.43409,0.19908" id="path11109-3-7" marker-end="none" marker-start="url(#Arrow2Lstart-9)" stroke-miterlimit="4" stroke-width="2.19348" stroke="#000000" fill="none"/>
<path d="m536.6307,515.34929l46.93627,0.19907" id="path11109-3-7-3" marker-end="none" marker-start="url(#Arrow2Lstart-9)" stroke-miterlimit="4" stroke-width="1.98292" stroke="#000000" fill="none"/>
</g>
</g>
</svg>
\ No newline at end of file
......@@ -94,7 +94,7 @@
</item>
<item>
<key> <string>content_md5</string> </key>
<value> <string>32afe1f69ab590a99b434c334cb56e5b</string> </value>
<value> <string>9e5564507078d39a1cb9abcea66adff9</string> </value>
</item>
<item>
<key> <string>content_type</string> </key>
......@@ -293,11 +293,13 @@
</item>
<item>
<key> <string>actor</string> </key>
<value> <string>supertristan</string> </value>
<value> <string>klaus.woelfel</string> </value>
</item>
<item>
<key> <string>comment</string> </key>
<value> <string>touched for reconversion</string> </value>
<value>
<none/>
</value>
</item>
<item>
<key> <string>error_message</string> </key>
......@@ -323,7 +325,7 @@
</tuple>
<state>
<tuple>
<float>1468329684.73</float>
<float>1469717523.37</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -5,6 +5,20 @@
<footer>
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>.
</footer>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section class="">
<h1>Agenda</h1>
<ul>
......@@ -14,9 +28,16 @@
<li>How to publish the second version</li>
<li>How to use fast contribution</li>
</ul>
<details open="open">
<p>In this presentation, we are going to explain how to create and release a document, prepare and publish the second version, as well as the fast contribution way to document module.</p>
</details>
</section><section class="screenshot">
<h1>Manage Document Versioning</h1>
<img alt="Manage Document Versioning" title="Manage Document Versioning" type="image/png" src="http://img.erp5.cn/osoe-howto-manage.document.versioning-screenshot?format=png">
<details open="open">
<p>In an organisation, it happens very often that a document has different versions for different purposes. In order to manage all your documents in the right order,
it is important to firstly manage document versioning.</p>
</details>
</section><section class="screenshot">
<h1>Create a new document</h1>
<img alt="Create a new document" title="Create a new document" src="http://img.erp5.cn/osoe-howto-create.new.document.versioning-screenshot?format=png" type="image/png">
......@@ -57,7 +78,10 @@
<b>Version</b>: you must choose the version of the document. Start at 001, then increase it for each version
</p><p>
<b>Language</b>: choose the language of the document. Should be two letters according to the ISO601 standard for languages. It will be used to display the proper document depending of the language of the interface.
</p><p>You have a field where you can add the name(s) of the contributor(s).</p><p>
</p><p>You have a field where you can add the name(s) of the contributor(s).</p>
</details>
<details open="open">
<p>
Then you have to <b>choose the classification</b> of the document. The Classification defines who can access, modify or use this document.
</p><p>
Then comes <b>few categories which will allow you to classify</b> your document as you would have done with a paper document. You will choose the Group and the site it refer to. Then the function of the document if it has one. Finally you can <b>choose one or more publication section</b> for the document.
......@@ -92,7 +116,8 @@
</p><p>
<b>Share</b>: Sharing the document is used to share it within a specific area of users which can log into your system. Depending on the Classification of the document, And users rôle within groups or projects, users of your instance will be able to see the document or not.
</p><p>
<b>Publish</b>: Publishing a document will make it completely public. You can then give the URL to anyone, he will be able to see it: https://www.tiolive.com/<b>instanceID</b>/document_module/<b>document.reference</b>/view
<b>Publish</b>: Publishing a document will make it completely public. You can then give the URL to anyone, he will be able to see it:
</p><P>https://www.tiolive.com/<b>instanceID</b>/document_module/<b>document.reference</b>/view
</p>
</details>
</section><section class="screenshot">
......
......@@ -250,7 +250,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.43310.4661.45725</string> </value>
<value> <string>952.53031.50721.24369</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -268,7 +268,7 @@
</tuple>
<state>
<tuple>
<float>1468942952.44</float>
<float>1469526228.73</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -4,6 +4,20 @@
<footer>
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>.
</footer>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section class="">
<h1>Agenda</h1>
<ul>
......@@ -11,11 +25,14 @@
<li>How to fill the Category Spreadsheet</li>
<li>How to distinguish the different categories from each other</li>
</ul>
<details open="open">
<p>The guide will teach you how to fill the category spreadsheet, containing general advice as well as a detailed description of each category.</p>
</details>
</section><section class="illustration">
<h1>What do you need categories for?</h1>
<img alt="What do you need categories for?" title="What do you need categories for?" src="http://img.erp5.cn/P-CLOUDIA-Category.Spreadsheet.HowTo.Spreadsheet.Transfer.Information?format=png" type="image/svg+xml">
<details open="open">
<p>Spreadsheets are used to transfer the configuration information from the real world into the ERP5 system, in order to configure an ERP system.</p><p>The guide will teach you how to fill the category spreadsheet, containing general advice as well as a detailed description of each category.</p>
<p>Spreadsheets are used to transfer the configuration information from the real world into the ERP5 system, in order to configure an ERP system.</p>
</details>
</section><section class="">
<h1>Category Configuration Example</h1>
......@@ -81,7 +98,10 @@
<h1>Role</h1>
<img alt="Role" title="Role" src="http://img.erp5.cn/P-CLOUDIA-Category.Spreadsheet.HowTo.Role?format=png" type="image/svg+xml">
<details open="open">
<p>In this sheet, describe the roles of the organization. People have different roles in the company. A possible configuration is:</p><p>- internal: A company, an office or a person within the company's group</p><p>- external: Persons who work for the organisation, but they are not permanent employees, such as temporary staff, leased laborer, consultant, etc.</p><p>- client: A client which buys goods or services from the company group</p><p>- supplier: A supplier which provides goods or services to the company group</p><p>- administration: An administrative body (ex. tax office, registration office)</p><p>- sales lead: A person or an organisation that is potentially interested in purchasing a product or service from the company group (first stage in sales process)</p><p>- sales prospect: A person or an organisation that is interested in purchasing a product or service from the group (qualified sales lead)</p><p>- user: User is for example a user of an online forum of the company, it may not be a client of the company.</p><p>- member: For some association or organisation which are not a company, there are members (active member who are voted into the board to have decision right, and non-active members).</p><p>These roles are proposals and have to be checked for completeness and applicability in your company.</p>
<p>In this sheet, describe the roles of the organization. People have different roles in the company. A possible configuration is:</p><p>- internal: A company, an office or a person within the company's group</p><p>- external: Persons who work for the organisation, but they are not permanent employees, such as temporary staff, leased laborer, consultant, etc.</p><p>- client: A client which buys goods or services from the company group</p><p>- supplier: A supplier which provides goods or services to the company group</p><p>- administration: An administrative body (ex. tax office, registration office)</p><p>- sales lead: A person or an organisation that is potentially interested in purchasing a product or service from the company group (first stage in sales process)</p>
</details>
<details open="open">
<p>- sales prospect: A person or an organisation that is interested in purchasing a product or service from the group (qualified sales lead)</p><p>- user: User is for example a user of an online forum of the company, it may not be a client of the company.</p><p>- member: For some association or organisation which are not a company, there are members (active member who are voted into the board to have decision right, and non-active members).</p><p>These roles are proposals and have to be checked for completeness and applicability in your company.</p>
</details>
</section><section class="illustration">
<h1>Grade</h1>
......@@ -93,7 +113,10 @@
<h1>Region</h1>
<img alt="Region" title="Region" src="http://img.erp5.cn/P-CLOUDIA-Category.Spreadsheet.HowTo.Region?format=png" type="image/svg+xml">
<details open="open">
<p>Please fill here the list of regions and counties in the world according to your point of view.</p><p>UNO standards exist for this. However, they do not cover business concepts such as EMEA (Europe, Middle East, Asia). Moreover, the choice of a list of regions includes both commercial and political consequences.</p><p>For example, it is usual when sending a letter to Barcelona to locate Barcelona in Catalunya, Espagne (French is the standard for international mail). This would not be the case in France where few people consider writing to someone in Lyon, Rhone-Alpes, France but would write to someone in Lyon, France.</p><p>Consider also the case of Corsica which is more sensitive, or of any region in which part of its inhabitants consider that they belong to a country which aims at becoming independent from what they view as an occupation force. There numerous examples of this kind, including Taiwan which is a major industrial country and which is not considered as such by UNO.</p><p>Another example is Japan, which most inhabitants consider that they are not part of Asia (China is part of Asia for them). Doing business in Asia often requires a special treatment for Japan, which is considered as a continent on its own, whereas China influenced countries are put in a single group.</p><p>We advice you making your own classification of regions in the world and making it as independent as possible of future changes (will Taiwan be part of China in 10 years ? will New Caledonia become independent in 5 years ?). Geopolitics may evolve, but business remains.</p><p>Regions need also sometimes a higher level of precision, but not uniformly. A European business does not care about states in the USA. However, a USA business needs to keep track of its clients based on the state information. USA states should therefore appear in the region category for a USA business. The same is true for a Japanese business, which probably needs prefectures (ex. Kanagawa) yet does not use very often the political concept of "region" (ex. Chubu) which does not make much sense usually in Japanese business culture. And a local business may require a precision at the level of the different areas in the same city.</p>
<p>Please fill here the list of regions and counties in the world according to your point of view.</p><p>UNO standards exist for this. However, they do not cover business concepts such as EMEA (Europe, Middle East, Asia). Moreover, the choice of a list of regions includes both commercial and political consequences.</p><p>For example, it is usual when sending a letter to Barcelona to locate Barcelona in Catalunya, Espagne (French is the standard for international mail). This would not be the case in France where few people consider writing to someone in Lyon, Rhone-Alpes, France but would write to someone in Lyon, France.</p><p>Consider also the case of Corsica which is more sensitive, or of any region in which part of its inhabitants consider that they belong to a country which aims at becoming independent from what they view as an occupation force. There numerous examples of this kind, including Taiwan which is a major industrial country and which is not considered as such by UNO.</p>
</details>
<details open="open">
<p>Another example is Japan, which most inhabitants consider that they are not part of Asia (China is part of Asia for them). Doing business in Asia often requires a special treatment for Japan, which is considered as a continent on its own, whereas China influenced countries are put in a single group.</p><p>We advice you making your own classification of regions in the world and making it as independent as possible of future changes (will Taiwan be part of China in 10 years ? will New Caledonia become independent in 5 years ?). Geopolitics may evolve, but business remains.</p><p>Regions need also sometimes a higher level of precision, but not uniformly. A European business does not care about states in the USA. However, a USA business needs to keep track of its clients based on the state information. USA states should therefore appear in the region category for a USA business. The same is true for a Japanese business, which probably needs prefectures (ex. Kanagawa) yet does not use very often the political concept of "region" (ex. Chubu) which does not make much sense usually in Japanese business culture. And a local business may require a precision at the level of the different areas in the same city.</p>
</details>
</section><section class="illustration">
<h1>Region</h1>
......
......@@ -422,7 +422,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.43317.10171.63008</string> </value>
<value> <string>952.53043.4931.12572</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -440,7 +440,7 @@
</tuple>
<state>
<tuple>
<float>1468943368.31</float>
<float>1469526987.21</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -5,20 +5,34 @@
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>.
</footer>
<details open="open">
<p>Now you have worked through the tutorials to understand ERP-Systems, we will now start to perform a consulting process for an ERP implementation using the on-line questionnaire system. In this presentation, you will know what do you have to prepare for this task and understand what the ERP Consulting and Configuration Questionnaire is needed for.</p>
</details>
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section style="opacity: 1;" class="">
<h1>Agenda</h1>
<ul>
<li>The interview and the quetionnaire</li>
<li>The interview and the questionnaire</li>
<li>Preceding steps for the interview</li>
<li>Questionnaire objectives</li>
</ul>
<details open="open">
<p>Now you have worked through the tutorials to understand ERP-Systems, we will now start to perform a consulting process for an ERP implementation using the on-line questionnaire system. In this presentation, you will know what do you have to prepare for this task and understand what the ERP Consulting and Configuration Questionnaire is needed for.</p>
</details>
</section><section class="illustration">
<h1>The interview and the quetionnaire</h1>
<img alt="The interview and the quetionnaire" title="The interview and the quetionnaire" style="display: block; margin: 0pt auto;" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.Interview.And.Questionnaire?format=png" type="image/svg+xml">
<details open="open">
<p>Our interview is a bilateral process between the interviewer and the interviewee - the company. A questionnaire is used to extract information about the company in a way which allows for the ERP configuration to be filled. The results of the interview will be transferred on-line.</p>
<p>Our interview is a bilateral process between the interviewer and the interviewee - the company. A questionnaire is used to extract information about the company in a way which allows for the ERP configuration to be filled. The results of the interview shall be able to be transferred on-line.</p>
</details>
</section><section class="">
<h1>Preceding steps</h1>
......
......@@ -420,7 +420,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.32883.35178.42461</string> </value>
<value> <string>952.57996.13428.59665</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -438,7 +438,7 @@
</tuple>
<state>
<tuple>
<float>1468943052.18</float>
<float>1469824405.22</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -5,14 +5,28 @@
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>.
</footer>
<details open="open">
<p>Now we will focus on how to execute the interview and evaluate the answers we get from the interview. This tutorial will show you what constitutes a good answer, and discuss some questions in details.</p>
</details>
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section class="">
<h1>Agenda</h1>
<ul>
<li>How to provide high quality answers</li>
<li>Question descriptions</li>
</ul>
<details open="open">
<p>Now we will focus on how to execute the interview and evaluate the answers we get from the interview. This tutorial will show you what constitutes a good answer, and discuss some questions in details.</p>
</details>
</section><section class="illustration">
<h1>What is a good answer?</h1>
<img alt="What is a good answer?" title="What is a good answer?" style="display: block; margin: 0pt auto;" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Good.Answer?format=png" type="image/svg+xml">
......@@ -22,6 +36,30 @@
</section><section class="illustration">
<h1>What is a bad answer?</h1>
<img alt="What is a bad answer?" title="What is a bad answer?" style="display: block; margin: 0pt auto;" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Bad.Answer?format=png" type="image/svg+xml">
<details open="open">
<p>
Here are the 4 terms frequently used by executives to hide the fact that they are not able to define what they precisely expect from an ERP: <strong>cost</strong>, <strong>strategy</strong>,
<strong>productivity</strong> and <strong>communication</strong>.Those terms are forbidden subjects in this lecture.
In other contexts, they could be useful terms. But here, they are reallly not.
</p>
<p>
For example, caring too much about specific way of computing a cost will have no impact on being able to deliver products in time. Cost does not even have any impact on cash, except very indirectly through the ability to obtain
a bank loan by producing financial reports based on a cost formula that maximises EBITDA. This is not the role of an ERP, but of an external reporting system. This external
reporting system needs nothing else but accurate data extracted from the ERP.
</p>
<p>
About strategy, executives often mention this word to hide the fact that they have no actual priorities for their ERP implementation.
</p>
<p>
Productivity - sometimes mentionned as efficient user interface - is also a way to escape from defining clear goals in terms of quantitative management. Real productivty derives
from automation: an executive who has clear goals with thus explain how he plans to change organisation with the ERP and which part can be automated.
</p>
<p>
Communication is the last forbidden word. It refers often to the idea of the right information at the right time - which is not a bad idea - but it can only be achieved
in an ERP and possibly with any management software by defining organisation processes of which the side effect is to bring that right information at the right time to the right person.
We thus forbid this work too in order to ensure that executives define that organisation process.
</p>
</details>
</section><section class="illustration">
<h1>What is a good answer - Example</h1>
<img alt="What is a good answer - Example" title="What is a good answer - Example" style="display: block; margin: 0pt auto;" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Answer.Example?format=png" type="image/svg+xml">
......
......@@ -423,7 +423,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.43315.6111.6168</string> </value>
<value> <string>952.53041.20417.49828</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -441,7 +441,7 @@
</tuple>
<state>
<tuple>
<float>1468943246.3</float>
<float>1470044188.23</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -5,8 +5,19 @@
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>.
</footer>
<details open="open">
<p>This tutorial will show you how to fill in the questionnaire and how to improve your answer set. Remeber, after your first answer set was reviewed and requested, you need to submit the improved version for peer review.</p>
</details>
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section class="">
<h1>Agenda</h1>
<ul>
......@@ -14,6 +25,9 @@
<li>How to improve your answers</li>
<li>How to submit your answer set for peer review</li>
</ul>
<details open="open">
<p>This tutorial will show you how to fill in the questionnaire and how to improve your answer set. Remember, after your first answer set was reviewed and requested, you need to submit the improved version for peer review.</p>
</details>
</section><section class="">
<h1>Fill in the answer on-line</h1>
<p>The following slides show you how to fill the questionnaire on-line.</p>
......@@ -205,11 +219,6 @@
your changes.
</p>
</details>
</section><section class="">
<h1>Submit your Answer Set for peer review (For Students)</h1>
<details open="open">
<p>After you finished improving your answer set the first time, you need to submit it for peer review.</p>
</details>
</section><section class="screenshot">
<h1>Click on "Submit for Peer Review"</h1>
<img alt="Submit again your improved Answer Set for peer review" title="Submit again your improved Answer Set for peer review" type="image/svg+xml" src="https://www.erp5.com/P-CLOUDIA-Configuration.Questionnaire.HowTo.Submit.For.Peer.Review?format=png">
......
......@@ -423,7 +423,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.32885.33508.22796</string> </value>
<value> <string>952.58027.5952.19676</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -441,7 +441,7 @@
</tuple>
<state>
<tuple>
<float>1468943124.13</float>
<float>1470061712.16</float>
<string>UTC</string>
</tuple>
</state>
......
<section>
<h1>Accounting for Mathematicians</h1>
<footer>by <a href="http://www.osoe-project.org/contact">OSOE Project </a></footer>
<footer>by <a href="http://www.osoe-project.org/contact">OSOE Project </a></footer>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section> <section>
<h1>Agenda</h1>
<ul>
......@@ -12,16 +26,24 @@
<li>Reports</li>
<li>Profits</li>
</ul>
<details open="open">
<p>The goal of this lesson is to teach accounting in a way which will be valid in the next 100 years or more. For that purpose, we introduce in the lesson
the concepts of accounting using a set theory formalism.</p>
<p>We believe that too much fashion, too many fuzzy words are used in the current approaches of accounting education. Students learn about the so-called
general accounting, which is not general at all and which is usually presented in a way which is specific to each legislation. Students learn about
the so-called cost accounting, which has no relation to costs. Students learn about analytical accounting, with a singular, instead of learning about
accounting analytics, with a plural. Students learn about activity based accounting, which is just one example of accounting analytics.</p>
<p>We hope, through this lesson, to exhibit the concept of universal accounting in such a way that students can learn a model which is useful to
understand and explain all the types of accounting which exist or will be created in the near or distant future, based on the ever evolving fashion
in corporate management.</p>
</details>
</section> <section>
<h1>The Account Space: A</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-OSOE-Accounting.Mathematician-Account.SpaceA?format=" /> <details open="true">
<p>The goal of this lesson is to teach accounting in a way which will be valid in the next 100 years or more. For that purpose, we introduce in the lesson the concepts of accounting using a set theory formalism.</p>
<p>We believe that too much fashion, too many fuzzy words are used in the current approaches of accounting education. Students learn about the so-called general accounting, which is not general at all and which is usually presented in a way which is specific to each legislation. Students learn about the so-called cost accounting, which has no relation to costs. Students learn about analytical accounting, with a singular, instead of learning about accounting analytics, with a plural. Students learn about activity based accounting, which is just one example of accounting analytics.</p>
<p>We hope, through this lesson, to exhibit the concept of universal accounting in such a way that students can learn a model which is useful to understand and explain all the types of accounting which exist or will be created in the near or distant future, based on the ever evolving fashion in corporate management.</p>
<p>The first concept in accounting is the <strong>Account</strong>. An account is a point in an arbitrary N-dimensional discrete space. Some people like to give names to those dimensions, names which will likely become irrelevant in a century. Dimension 1 is called “General Account”. It represents the economic nature of the account: income, expense, inventory, etc. Dimension 2, the “Party”, represents a supplier, a client, a business unit or any 3rd party. Dimension 3, the “Project”, represents a project in a company which does project management. Dimension 4, the “Activity”, represents activities such as gardening. More dimensions could be used to provide more powerful accounting analytics.</p> </details> </section> <section>
<h1>Legislation: L</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-OSOE-Accounting.Mathematician-Legislation.l?format=" /> <details open="true">
<p>Governments, especially in countries of Civil Law, like to define an official space of accounts, called <strong>L</strong>. This space of account contains usually a few thousand standard account names which are required to be used to produce legislation dependent tax reports and exchange data.</p>
<p>This space of account can evolve. Many accountants believe that Dimension 1 of the space of accounts is the space of accounts provided by the government. This creates a lot of troubles each time the legislation changes or whenever a company has subsidiaries in different countries. </p>
<p>To solve all these problems, we define here a Legislation L as a mapping between the space of Accounts A and a single dimension discrete space which represents one possible legislation. Thanks to this approach, called indirection, our space of accounts no longer depends on political fashion, a long as A is a superset of L.</p>
<p>To solve all these problems, we define here a Legislation L as a mapping between the space of Accounts A and a single dimension discrete space which represents one possible legislation. Thanks to this approach, called indirection, our space of accounts no longer depends on political fashion, as long as A is a superset of L.</p>
<p>In countries, especially in countries of Common Law, governments prefer to define accounting principles through quite ambiguous rules. Those rules are then interpreted by chartered accountants who use their legal expertise to create their own space of account. It is like the Legislation L is provided here by chartered accountants instead of being provided by the government.</p> </details> </section> <section>
<h1>The Currency Space: C</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-OSOE-Accounting.Mathematician-Currency.Space.C.formula?format=" /> <details open="true">
<p>Accounting lives in a world of currencies. We introduce a space of currencies: <strong>C</strong>. C is a single dimension discrete space. <strong>A</strong> currency exchange function E is also introduced, whether currencies can be really exchanged or not. The currency exchange space is required because most tax reports must be produced using a single currency, the currency of the country, although most companies use multiple currencies.</p>
......@@ -40,12 +62,12 @@
<p>Assets, a positive value, are displayed as a debit. Debts, a negative value, are displayed as credit.</p>
<p>Moreover, they consider that sales income are future profits, that profits are debts to the owner of the company, and that income should thus be considered as a negative value, just like debts. Just the same way, expenses are future losses, which will reduce the capital of the company, i.e. reduce a debt to the owner of the company, and should thus be considered positive values. It is a bit weird at first but consistent.</p>
<p>Income, a negative value, is displayed as credit. Expense, a positive value, is displayed as debit.</p>
<p>Now, where does this debit and credit invariant comes from? The sad truth is that this debit and credit invariant has no well defined rationale. Many companies in the world do accounting without following this invariant, even if accounts in countries of Civil Law hate to hear that.</p>
<p>Now, where does this debit and credit invariant comes from? The sad truth is that this debit and credit invariant has no well defined rationale. Many companies in the world do accounting without following this invariant, even if accountants in countries of Civil Law hate to hear that.</p>
<p>The only rationale of the debit and credit invariant is to help making sure that every transaction can be partitioned in 2 subsets of opposite total, consistently with the partitioning of accounts introduced later. However, it is not the only way to reach that goal.</p> </details> </section> <section>
<h1>Supplier &amp; Client Invariant</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-OSOE-Accounting.Mathematician-Supplier.Client.Invariant.formula?format=" /> <details open="true">
<p>The supplier and client invariant is a real and universal invariant which most accountants are not aware of. It relates to the principles of chemistry “nothing is created, nothing disappears, everything is transformed”.</p>
<p>What this invariant says is that whenever a supplier has an income, its client has an expense of equivalent amount, consistently with the exchange rate of the transaction currency.</p>
<p>This invariant applies to many situations, even in situations where the same company acts as supplier and as client. For example, amortization of an asset, could be represented with a single transaction line with same company in Dimension 2 of the space of accounts on both sides. The company at the source acts as a supplier and provides a share of machine which reduces the Immobilisation amount (an asset). The company at the destination acts as a client which consumes a share of machine, just like it would rent the machine, which is represented as an Expense. No other line is required since no cash is transferred and nothing would anyway appear at consolidation time. (XXX-JPS NOT SURE - CHECK IF CONSISTENT WITH CONSOLIDATION). Another common example is the case of currency transfer, which is represented much more efficiently with a single transaction with same company at both ends. Last but not least, some companies prefer to enter only a single for every sales they make and then, at the end of the month, gather all sales transactions into a single receivable.</p>
<p>This invariant applies to many situations, even in situations where the same company acts as supplier and as client. For example, amortization of an asset, could be represented with a single transaction line with same company in Dimension 2 of the space of accounts on both sides. The company at the source acts as a supplier and provides a share of machine which reduces the Immobilisation amount (an asset). The company at the destination acts as a client which consumes a share of machine, just like it would rent the machine, which is represented as an Expense. No other line is required since no cash is transferred and nothing would anyway appear at consolidation time. Another common example is the case of currency transfer, which is represented much more efficiently with a single transaction with same company at both ends. Last but not least, some companies prefer to enter only a single for every sales they make and then, at the end of the month, gather all sales transactions into a single receivable.</p>
<p>In short: the invariance of Debit &amp; Credit is a myth, the supplier and client invariance is universal.</p> </details> </section> <section>
<h1>Tax Report</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-OSOE-Accounting.Mathematician-Tax.Report.formula?format=" /> <details open="true">
<p>Tax reports are made by calculating the total of transaction amounts expressed in the national currency of a single organisation for a subset of the space of accounts. Both source and destination amounts should be taken into account since the organisation for which the tax report is calculated could appear on both side.</p>
......
......@@ -90,6 +90,7 @@
<string>group/nexedi</string>
<string>contributor/person_module/510</string>
<string>contributor/person_module/20130927-61A66CC</string>
<string>contributor/person_module/jps</string>
</tuple>
</value>
</item>
......@@ -278,7 +279,7 @@
</item>
<item>
<key> <string>actor</string> </key>
<value> <string>ni.yan</string> </value>
<value> <string>jp</string> </value>
</item>
<item>
<key> <string>comment</string> </key>
......@@ -292,7 +293,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.43303.46950.49981</string> </value>
<value> <string>952.61428.1761.55263</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -310,7 +311,7 @@
</tuple>
<state>
<tuple>
<float>1468942567.07</float>
<float>1470030581.82</float>
<string>UTC</string>
</tuple>
</state>
......
<section class="master">
<h1>Session 1: Careers and Assignments</h1> <img alt="Workflow of people's career" type="image/png" title="Career and assignments workflow" src="http://img.erp5.cn/osoe-Careers.And.Assignments.Front.Page.Career.Workflow?format=png" /> <footer>
by <a href="/contact">OSOE Project</a>.
</footer> </section><section>
</footer>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section>
<h1>Agenda</h1>
<ul>
<li>Person and organisations</li>
......
......@@ -126,6 +126,7 @@
<string>contributor/person_module/20110503-EE9699</string>
<string>contributor/person_module/851</string>
<string>contributor/person_module/20130927-61A66CC</string>
<string>follow_up/product_module/148</string>
</tuple>
</value>
</item>
......@@ -428,7 +429,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.43180.10614.37484</string> </value>
<value> <string>952.53181.50613.54073</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -446,7 +447,7 @@
</tuple>
<state>
<tuple>
<float>1468935171.09</float>
<float>1471593170.62</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -5,14 +5,51 @@
<footer>
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>
</footer>
</section><section>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p>This chapter introduces the lecture goal, organisation and evaluation.</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section>
<section>
<h1>Agenda</h1>
<ul>
<li>What are the objectives of the course</li>
<li>How the sessions are organised</li>
<li>How you will be evaluated</li>
</ul>
</section><section class="">
<details open="open">
<p>In this presentation, we are going to explain how this lecture was designed. First, we define the goals of the course and especially what students can expect to learn by
attending the course. Second, we explain the organisation of the lecture as a sequence of theory and tutorials that cover the different aspects of an ERP. Last we introduce
the student evaluation process based on a case study and questionnaire.
</p>
</details>
</section>
<section class="">
<h1>Course Objectives</h1>
<ul>
<li>Learn universal and fundamental workflow of companies</li>
......@@ -21,7 +58,7 @@
<li>Being capable of configuring an ERP</li>
</ul>
<details open="open">
<p>"ERP: Theory, Practice and Configuration" is a lesson which has three main goals.</p><ul>
<p>"ERP: Theory, Practice and Configuration" is a lesson which has four main goals.</p><ul>
<li>The first one is to teach you the universal and fundamental workflow of the companies. By doing so, you will be able to understand how is organised any company and how ERP systems help companies to improve their performance by managing their business process.</li>
<li>The second step is to see how the theoretical workflow is applied in an ERP. For this we will use ERP5 instances delivered to each student of this course. You will then be able to use it as companies do everyday.</li>
<li>The third goal is to teach how to perform an initial consulting process for an ERP implementation. We will use an online questionnaire with the most important questions to ask to a company during this process. The objective of the questionnaire is to identify those business processes which are not successful enough and which can be improved using an ERP. The objective is to understand how to set the priorities for an ERP implementation.</li>
......@@ -50,7 +87,10 @@
<h1>Session 2: CRM Tickets and Events</h1>
<img alt="Session 2: CRM Tickets and Events" title="Session 2: CRM Tickets and Events" src="http://img.erp5.cn/P-OSOE-ERP.Configuration.Introduction.CRM.Tickets.And.Events?format=jpg" type="image/png">
<details open="open">
<p>Session two is the Customer Relationship Management (CRM) part of the ERP system.</p><p>We will study Tickets and Events, and their specific workflows. Events are documents in the system which represent every interaction we have with our customers, our suppliers etc.</p><p>Recording every "Event" which occurred during the company's activity will help us to learn more about our customers and our suppliers. Further information about what have been done with or said to a specific person will be available to persons who need it.</p><p>Tickets are documents in ERP5 which can contain other documents such as Events or documents from the Document Management System (DMS).</p><p>Having such records will help you to organise and follow your interaction with persons outside the company. Specific workflows are applied to Tickets depending of their nature.</p><p>In ERP5 we have four kinds of Tickets: the Campaigns, the Sale Opportunities, the Support Requests and the Meetings. Each one will be studied during this session.</p><p>Then five tutorials will be followed:</p><ul>
<p>Session two is the Customer Relationship Management (CRM) part of the ERP system.</p><p>We will study Tickets and Events, and their specific workflows. Events are documents in the system which represent every interaction we have with our customers, our suppliers etc.</p><p>Recording every "Event" which occurred during the company's activity will help us to learn more about our customers and our suppliers. Further information about what have been done with or said to a specific person will be available to persons who need it.</p><p>Tickets are documents in ERP5 which can contain other documents such as Events or documents from the Document Management System (DMS).</p><p>Having such records will help you to organise and follow your interaction with persons outside the company. Specific workflows are applied to Tickets depending of their nature.</p><p>In ERP5 we have four kinds of Tickets: the Campaigns, the Sale Opportunities, the Support Requests and the Meetings. Each one will be studied during this session.</p>
</details>
<details open="open">
<p>Then five tutorials will be followed:</p><ul>
<li>"How to create Campaigns" will teach you how to create new Campaigns in ERP5.</li>
<li>"How to create Events in Campaigns" will teach you how to create new Events from an existing Campaign in ERP5, you will then see how phone calls, emails, fax etc., look like in such systems.</li>
<li>"How to post outgoing Events" will teach you how you can send Events such as emails directly from ERP5.</li>
......
......@@ -93,6 +93,7 @@
<string>contributor/person_module/20111027-2BE16E4</string>
<string>contributor/person_module/510</string>
<string>contributor/person_module/20121115-586BC0F</string>
<string>contributor/person_module/20130927-61A66CC</string>
</tuple>
</value>
</item>
......@@ -285,7 +286,7 @@
</item>
<item>
<key> <string>actor</string> </key>
<value> <string>sven</string> </value>
<value> <string>ni.yan</string> </value>
</item>
<item>
<key> <string>comment</string> </key>
......@@ -299,7 +300,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.32887.21262.59741</string> </value>
<value> <string>952.53175.49920.11670</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -317,7 +318,7 @@
</tuple>
<state>
<tuple>
<float>1468931897.4</float>
<float>1469543163.1</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -2,13 +2,37 @@
<h1>OSOE - ERP 101</h1> <img alt="OSOE - ERP 101" title="OSOE - ERP 101" src="http://img.erp5.cn/osoe-erp-101.cover?format=png" type="image/png" /> <footer>
by <a href="/contact">OSOE Project</a>.
</footer> <details open="true">
<p>ERPs are usually considered as a difficult matter to learn or to teach. ERP classes can be so general, that nothing is really learned. Or they can be based on case studies, and thus lack of any strong teaching in terms of theoretical principles. Or they can be so much linked to a given product that what people learn is the product, rather than universal and permanent principles. ERPs are also considered to be such a huge, complex pipe factory, that many people even believe that they can not be taught. In this class, we are going to change the way that ERPs were taught.</p> </details> </section><section>
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details> </section><section>
<h1>Agenda</h1>
<ul>
<li>Class requirements</li>
<li>ERP facts</li>
<li>What is an ERP</li>
</ul> </section><section class="illustration">
</ul>
<details open="true">
<p>ERPs are usually considered as a difficult matter to learn or to teach. ERP classes can be so general, that nothing is really learned.
Or they can be based on case studies, and thus lack of any strong teaching in terms of theoretical principles. Or they can be so much linked
to a given product that what people learn is the product, rather than universal and permanent principles. ERPs are also considered to be such
a huge, complex pipe factory, that many people even believe that they can not be taught. In this class, we are going to change the way that ERPs were taught.</p>
<p>
We are going to introduce some basic facts that every student should know before starting the course: such as who needs an ERP, the cost of
an ERP implementation, the key players in this field, ect. Then we will give a very specific definition on ERP. By knowing all these information, student
will be able to start searching for a suitable organisation/company for his/her case study at the end of the course.
</p>
</details>
</section><section class="illustration">
<h1>Requirements</h1> <img src="http://img.erp5.cn/osoe-erp.101.requirements-screenshot?format=png" type="image/png" title="Requirements" alt="Requirements" /> <details open="true">
<p>The main requirement for this class is to find an implementation field. The best way to understand ERPs is to learn how to configure an ERP. And the best way to learn the configuration of ERPs is to actually configure it on a real case. We therefore require each student of this class to find a small business, a non profit organisation, a public administration, etc. which will serve as a implementation field.</p>
<p>The configuration process will happen after the 6th session. It will only require to fill a spreadsheet, which means that it is quite straightforward from a technical point of view. However, from the user point of view, this simple configuration will completely change the way the ERP is perceived. At the end ERP will match the business environment of the implementation field and become usable and very useful.</p>
......@@ -44,7 +68,7 @@
<p>If we translate these figures to a small company (6 people), we will find that implementing an ERP costs about 10,000 EUR in a small company or 20 man days. In a large organisation with 1,000 employees, an ERP will implementation will quickly reach 2,000 man days or 1,000,000 EUR. In a large multinational with 100,000 employees, an ERP implementation can quickly surpass 100,000 man days and 100,000,000 EUR.</p>
<p>At the same time, the cost of selling an ERP, which is mostly the time spent in convincing prospects to adopt a given ERP, does not change so much between a small company and a mid size company.</p>
<p>As a result, ERPs are not used very often by small companies, only because nobody is willing to spend time convincing them to adopt them and make no profit out that.</p> </details> </section><section class="illustration">
<h1>What is the success rate?</h1> <img alt="What is the success rate?" title="What is the success rate?" src="http://img.erp5.cn/osoe-what.is.success.rate-screenshot?format=png" type="image/png" /> <br /> <a href="http://www.erp5.org/sections/erp/mourlon-neyer.pdf/downloadFile/file/mourlon-neyer.pdf">mourlon-neyer.pdf</a><details open="true">
<h1>What is the success rate?</h1> <img alt="What is the success rate?" title="What is the success rate?" src="http://img.erp5.cn/osoe-what.is.success.rate-screenshot?format=png" type="image/png" /> <br /> <a href="https://www.erp5.com/allerp.pdf">allerp.pdf</a><details open="true">
<p>The “Mourlon Neyer” report is one of the best sources to understand the risk of ERPs. As a rule of thumb, 50% ERP projects fail, they cost 3 times as much as expected and take twice longer than planned.</p>
<p>The reasons for failure are very seldom related to the ERP software itself, but rather to the abnormal behavior of clients of consultants. However, because clients and consultants seldom accept to recognize their own mistakes, the ERP software is often blamed for the failure of the project by either the client or the consultant.</p>
<p>In this environment, where the one which is not to blame is blamed and those who should be blamed are not, only those ERPs with a strong brand can survive a 50% failure rate, together with ERP software which implementation is strictly controlled by the software publisher.</p>
......@@ -142,6 +166,15 @@
<p>If one notices that e-commerce is after all sales on the Web, that e-procurement is after all purchase on the Web, e-recruitment is HR on the Web, one can foresee what the combination of Web and an ERP could be: e-business, which is opening through the Web the corporate ERP to all partners of a company. Since business are increasingly distributed and relying on outsourcing and outside partners, it is a natural tendency for ERPs to become e-business tools.</p>
<p> <u>We could therefore claim that “support of e-business” is a frequent characteristic of a modern ERP</u>.
</p> </details> </section><section class="screenshot">
<h1>One ERP per student programme</h1> <img alt="One ERP per student programme" title="One ERP per student programme" src="http://img.erp5.cn/user-OSOE.Website.Homepage?format=png" type="image/png" /> </section>
<h1>One ERP per student programme</h1> <img alt="One ERP per student programme" title="One ERP per student programme" src="http://img.erp5.cn/user-OSOE.Website.Homepage?format=png" type="image/png" />
<details open="open">
<p>
This closes the introduction session about the ERP concept. However, this introduction can only be undertsood by <strong>patiently</strong> practicing a real ERP system
and going into the details of each of its main modules. Many managers dream about ERPs as a magical tool that eventually solves all management problems.
Their dream could easily turn into a nightmare because of exagerated expectations and lack of clear understanding of what a real ERP does or does not.
The follow-up sessions of this course are designed to provide students with the basic knowledge that will let them approach ERP implementation with realistic expectations.
</p>
</details>
</section>
<p> </p>
<p> </p>
\ No newline at end of file
......@@ -426,7 +426,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.43177.23057.51300</string> </value>
<value> <string>952.61676.12280.49621</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -444,7 +444,7 @@
</tuple>
<state>
<tuple>
<float>1468934959.7</float>
<float>1470045189.58</float>
<string>UTC</string>
</tuple>
</state>
......
<section class="illustration">
<h1>Session 2: CRM Tickets and Events - Events</h1> <img src="user-Events.Event.Workflow?format=png" type="image/png" alt="Event workflow" title="Event workflow" /> <footer>
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>.
</footer> <details open="open">
<p>Now we are going to present how a CRM is used to manage the communication within and outside your organsations.</p>
<p> <strong>Note: in this session &quot;CRM Tickets and Events&quot;, we will still use the examples of VIFIB to explain the concepts of &quot;Event&quot; and &quot;Ticket&quot; which are used to manage the interactions of a company with its contacts. So when you are practicing, please replace VIFIB with the company you created when you configured your ERP5 instance.</strong> </p> </details> </section><section>
</footer>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section>
<h1>Agenda</h1>
<ul>
<li>CRM</li>
......@@ -14,7 +27,14 @@
<li>The outgoing Event workflow</li>
<li>The incoming Event workflow</li>
<li>How to use worklists</li>
</ul> </section><section class="illustration">
</ul>
<details open="open">
<p>Now we are going to present how a CRM is used to manage the communication within and outside your organsations.</p>
<p> <strong>Note: in this session &quot;CRM Tickets and Events&quot;, we will still use the examples of VIFIB to explain the concepts of &quot;Event&quot;
and &quot;Ticket&quot; which are used to manage the interactions of a company with its contacts. So when you are practicing, please replace VIFIB with the
company you created when you configured your ERP5 instance.</strong> </p>
</details>
</section><section class="illustration">
<h1>CRM</h1> <img src="user-Events.CRM.System.In.ERP5?format=png" type="image/png" alt="CRM system: Person communication" title="Person communication" /> <details open="open">
<p>Due to the number of persons with whom we interact, and the growing number of communication tools of which only few leave a trace (eg, emails), and the difficulty of organising the trace of communication in a central system (eg, Emails are stored in personal mailboxes, Fax in a specific place etc.), the complexity of keeping trace of the communication within and outside of the organisation makes it difficult to learn from our experience and to share all the informations we have about one contact of our organisation. This gave birth to the CRM systems.</p>
<p>CRM stands for Customer Relationship Management. These systems have been created to keep track of every interaction that you have with your customers. Today, many CRM concepts can be applied to other fields. Based on the notion of &quot;Event&quot; and &quot;Ticket&quot;, they can also be used to track other forms of relations, such as your relations with suppliers, staff, media, etc. (eg, the Supplier Relation Management-SRM). So a CRM includes concepts of Events, Campaigns, Meetings, Sale Opportunities and Support Requests, is used for managing all the communication between our organisations and all the contacts.</p>
......@@ -91,7 +111,7 @@
<br />
This distinction is really important since you won't handle the same way the preparation of outgoing events and how you take care of incoming events.
</p>
<p>In our example, the Mail Message sent by VIFIB manager is an outgoing Event, while the replies from the his contacts are incoming Events.</p> </details> </section><section class="illustration">
<p>In our example, the Mail Message sent by VIFIB manager is an outgoing Event, while the replies from his contacts are incoming Events.</p> </details> </section><section class="illustration">
<h1>Keeping track of interactions: Event origin</h1> <img src="user-Events.Keep.Tracks.Of.Interactions.Event.Origin?format=png" type="image/png" alt="Keep track of interactions by 'Event Origin'" title="Keep track of interactions by 'Event Origin'" /> <details open="open">
<p>
By linking related Events together using <strong>&quot;Event Origin&quot;</strong>
......@@ -125,7 +145,8 @@
<strong>Follow Up</strong>
( &quot;Beta Developer Program&quot;). So these two features help us present complex interactions in a clear way.
<br /> </p> </details> </section><section class="illustration">
<h1>Outgoing Event workflow</h1> <img src="user-Events.Event.Workflow?format=png" type="image/png" alt="Outgoing Event workflow" title="Outgoing Event workflow" /> <details open="open">
<h1>Outgoing Event workflow</h1> <img src="user-Events.Event.Workflow?format=png" type="image/png" alt="Outgoing Event workflow" title="Outgoing Event workflow" />
<details open="open">
<p>The upper part of this illustration shows the workflow of Outgoing Events.</p>
<p>Depending on the assignment you have, you will be able to perform one or many actions on outgoing events.</p>
<p>
......@@ -166,6 +187,8 @@
the Event during the process.
</p>
<p>Under the direction of such a workflow, you can manage from a three-person organisation to a big call-center.</p>
</details>
<details open="open">
<p>
In our example, the <strong>Sender</strong>
Cédric de Saint Martin (community manager) created the Event as an
......@@ -175,7 +198,8 @@
is OK with everything, he will confirm the Event. When Cédric see the Event's state changed from &quot;draft&quot; to &quot;confirmed&quot;, he knows that the mail is approved and ready to be sent. After he sends the email to the
<strong>Receivers</strong>
- his contacts, the Event &quot;SlapOS Ongoing!&quot; would be stated as &quot;sent&quot;, and the Outgoing Event Process is finished.
</p> </details> </section><section class="screenshot">
</p>
</details> </section><section class="screenshot">
<h1>Worklists</h1> <img src="user-Events.Worklist.Outgoing?format=png" type="image/png" alt="Outgoing events worklist" title="Outgoing events worklist" /> <details open="open">
<p>The concept of workflow helps people to understand the entire process of handling Events. But it is abstract. In order to apply the workflow practically and efficiently, we will use the worklists.</p>
<p>
......@@ -186,9 +210,10 @@
</p>
<p>In our example, everyday, the VIFIB director Smets who is responsible for the operation of Events has to check &quot;My Favourites&quot; list to see how many &quot;Planned&quot; Events are waiting to be reviewed and confirmed. Among them, he will see the email created by VIFIB community manager Cédric, review it and set it as &quot;Confirmed&quot;. When Cédric checks &quot;My Favourites&quot; list and finds the email has been moved to the &quot;Confirmed&quot; list, he will send it, then the email will go into the &quot;Sent&quot; list.</p>
<p>So the Worklist makes the process precisely and clearly stated, and facilitates the work of everyone.</p> </details> </section><section class="illustration">
<h1>Incoming Event workflow</h1> <img src="user-Events.Event.Workflow?format=png" type="image/png" alt="Incoming Event workflow" title="Incoming Event workflow" /> <details open="open">
<h1>Incoming Event workflow</h1> <img src="user-Events.Event.Workflow?format=png" type="image/png" alt="Incoming Event workflow" title="Incoming Event workflow" />
<details open="open">
<p>
Incoming Events have a different workflow as shown in the second part of this illustration: they can either be created<strong>manually</strong>
Incoming Events have a different workflow as shown in the second part of this illustration: they can either be created <strong>manually</strong>
(e.g, you can
<strong>input</strong>
an email which is a support request or a reply from a customer to the company as a new incoming Event), or
......@@ -217,7 +242,7 @@
<br />
Thirdly, the recipient
<strong>create Follow Up Ticket</strong>
to record all the future interactions related to this Event, then the Event will been delivered automatically; you can also
to record all the future interactions related to this Event, then the Event will be delivered automatically; you can also
<strong>deliver</strong>
the Event directly after you receive it (state
&quot;
......@@ -232,6 +257,8 @@
</p>
<p>
The Final state &quot;delivered&quot; of incoming Event indicates to all the team members that this incoming Event has been acknowledged by the recipient to handle it. &nbsp; <br /> </p>
</details>
<details open="open">
<p>
In our example, after sending the email, VIFIB manager Cédric sent got a reply from one contact. So a new incoming Event will be created. Then the &quot;received&quot; Event can be processed in two ways: either be replied by Cédric the <strong>Recipient</strong>
directly, or be assigned to another person in the Support Team to handle the Event, just by changing the
......
......@@ -245,7 +245,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.43201.12144.36491</string> </value>
<value> <string>952.56139.33415.52172</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -263,7 +263,7 @@
</tuple>
<state>
<tuple>
<float>1468936493.84</float>
<float>1469712794.65</float>
<string>UTC</string>
</tuple>
</state>
......
<section class="illustration">
<h1>Session 3: Sale Orders</h1> <img alt="Sale Orders Workflow" title="Sale Orders Workflow" type="image/svg+xml" src="http://img.erp5.cn/P-OSOE-Order.Sale.Order.Workflow?format=png" /> <footer>
by <a href="/contact">OSOE Project</a> </footer> </section><section>
by <a href="/contact">OSOE Project</a> </footer>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section>
<h1>Agenda</h1>
<ul>
<li>The trade process</li>
......@@ -8,8 +23,8 @@
<li>What is a product</li>
<li>What are the conditions of a trade order?</li>
<li>The workflow of a sale order</li>
</ul> <details open="true">
<p>This guide has been created to teach the fundamentals of a sale/purchase order.</p>
</ul> <details open="true">
<p>This guide has been created to teach the fundamentals of a sale/purchase order.</p>
<p> <strong>
Note: in this session &quot;Sale Orders&quot;, we will use another company Hongzhao as an example to explain how to create products, trade conditions and sale orders in ERP5. Hongzhao is also configured when we installed another ERP5 instance, the same way as presented in the tutorial <a href="user-Howto.Configure.ERP5.for.SMB.With.Configurator/view">&quot;Configure your instance using ERP5 Configurator&quot;</a>. So when you are practicing, please replace Hongzhao with the company you created when you configured your ERP5 instance.
</strong> </p> </details> </section><section class="illustration">
......@@ -29,7 +44,7 @@
<p>An order represents a movement of resource (goods, services) from a company to another. So in every order we will have a source (the supplier) and a destination (the buyer). But the destination can be more than one person or even organisation.</p>
<p>About the destination, We must distinguish three things:</p>
<p>The person or organisation which receives the goods, the person or organisation which is invoiced, and the person which is taking the decision to buy. This is why on an order we must have three fields to let us represent correctly the reality.</p>
<p>To illustrate those, we can take a look at how is organised the supermarket in France. The companies have buying centres in which they negotiate the prices for all of their brands. It allows them to have more power in the negotiation. But once they have bought one hundred thousand yoghurt, they ask for them to be delivered in small quantities in each of their distribution centre. So we already have a different destination point from the person which takes the decision to buy. Then we might have to invoice the buying centre, and not the distribution centre</p>
<p>To illustrate those, we can take a look at how the supermarket is organised in France. The companies have buying centres in which they negotiate the prices for all of their brands. It allows them to have more power in the negotiation. But once they have bought one hundred thousand yoghurt, they ask for them to be delivered in small quantities in each of their distribution centre. So we already have a different destination point from the person which takes the decision to buy. Then we might have to invoice the buying centre, and not the distribution centre</p>
<p>We have also those kinds of distinction with the source of the movement.</p> </details> </section><section class="illustration">
<h1>A seller</h1> <img alt="A seller" title="A seller" type="image/png" src="http://img.erp5.cn/P-OSOE-Seller.Goods.and.Services?format=png" /> <details open="true">
<p>With the source of the movement, we will have a person who is responsible for the offer which has been made. This person is responsible for the client, or at least for the conditions of the transaction. But it doesn't mean that this person is in the same organisation which will deliver the goods or this person is not the one which will deliver the service.</p>
......
......@@ -295,7 +295,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.32894.7303.44065</string> </value>
<value> <string>952.52989.31072.27563</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -313,7 +313,7 @@
</tuple>
<state>
<tuple>
<float>1468941070.49</float>
<float>1469721667.97</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -5,6 +5,20 @@
<footer>
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>
</footer>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section class="">
<h1>Agenda</h1>
<ul>
......@@ -73,7 +87,10 @@
</p><p>Employees in charge of preparing the goods are then able to prepare the goods, and to enter which containers have been used, etc.</p><p>They can also decide not to send exactly what has been ordered. For example, they don't have all products which have been ordered.</p><p>
Once the Packing List has been prepared, they can mark the packing list as "Ready" to be shipped. We will then wait for the carrier to pick up the prepared packing list. <strong>Once they pick it up, we will mark the packing list as "Shipped". This will create the related invoice</strong>
.
</p><p>When the carrier tell us the the customer has received the goods, we can then mark the packing list as "Received".</p><p>When the customer receive the goods, he will check what has been delivered to him. So he or she will compare the packing list we provided to him with what he received. And an error is still possible. Either that we made a mistake while preparing, or maybe some packages have been damaged etc. So we need to wait until the customer accepts the delivery before marking the packing list as "Delivered".</p><p>
</p><p>When the carrier tell us the the customer has received the goods, we can then mark the packing list as "Received".</p><p>When the customer receive the goods, he will check what has been delivered to him. So he or she will compare the packing list we provided to him with what he received. And an error is still possible. Either that we made a mistake while preparing, or maybe some packages have been damaged etc. So we need to wait until the customer accepts the delivery before marking the packing list as "Delivered".</p>
</details>
<details open="open">
<p>
<strong>Note that if the goods ready to be shipped are different from what has been ordered, eg, the quantity is less, you can "Split and Defer" the Packing List before shipping them. In this way, ERP5 will create another Packing List for the remaining goods to be shipped as soon as they are prepared.</strong>
</p><p>Once you ship the Sale Packing List, a related Sale Invoice Transaction will be generated automatically for the next step of the trade process. We will talk about this in the following tutorials.</p>
</details>
......
......@@ -252,7 +252,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.43293.56539.10973</string> </value>
<value> <string>952.47199.19623.15156</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -270,7 +270,7 @@
</tuple>
<state>
<tuple>
<float>1468942016.22</float>
<float>1469524295.07</float>
<string>UTC</string>
</tuple>
</state>
......
<section class="screenshot">
<h1>Session 2: CRM Tickets and Events - Tickets</h1> <img alt="Ticket workflow" type="image/png" src="user-Tickets.Ticket.Workflow?format=png" title="Ticket workflow" /> <footer>
by <a href="http://www.osoe-project.org/contact">OSOE Project</a>.
</footer> <details open="open">
<p>From the presentation of Events, we have seen how the Event is used to trace every interaction between our employees and the outside world. It is really easy with events to keep track of a simple or complex interactions.</p>
<p>But what about parallel interactions? What if you organise a conference and you want to keep track of every interaction you have while you prepare the conference? This is not possible with only the Events. The same problem happens when you want to keep track of every discussion which occurs when you send a press release: in the same time you will start maybe one hundred or more discussions. This is why every CRM system uses what we call &quot;Tickets&quot;.</p> </details> </section><section>
</footer>
<details open="open">
<p>This visual guide is part of a collection of documents created by the One Student One ERP (OSOE)
project in collaboration with Institut Mines Telecom, Telecom Bretagne, Dresden University of Technology and
the South Westfalia University of Applied Sciences. It can be used to teach modern ERP theory and practice
to undergraduate students or professionals.
</p>
<p><b>Copyright</b>: You are free to copy, distribute, display, and perform the work under the following conditions: you must attribute
the work in the manner specified by the author or licensor; you may not use this work for any commercial purposes including training,
consulting, advertising, self-advertising, publishing, etc.; you may not alter, transform, or build upon this work. For any
reuse or distribution, you must make clear to others the license terms of this work. Any of these
conditions can be waived if you get permission from the copyright holder through a commercial license
or an educational license. For more information, contact info@nexedi.com
</p>
</details>
</section><section>
<h1>Agenda</h1>
<ul>
<li>What is a Ticket ?</li>
......@@ -13,7 +26,20 @@
<li>The workflow of a Sale opportunity</li>
<li>The workflow of a Support Request</li>
<li>The workflow of a Meeting</li>
</ul> <details open="open" /> </section><section class="screenshot">
</ul>
<details open="open">
<p>From the presentation of Events, we have seen how the Event is used to trace every interaction between our employees and the outside world.
It is really easy with events to keep track of a simple or complex interactions.</p>
<p>But what about parallel interactions? What if you organise a conference and you want to keep track of every interaction you have while you
prepare the conference? This is not possible with only the Events. The same problem happens when you want to keep track of every discussion
which occurs when you send a press release: in the same time you will start maybe one hundred or more discussions. This is why every CRM system
uses what we call &quot;Tickets&quot;.</p>
<p>
In this presentation, we are going to explain the Tickets in ERP5, by knowing the definition of a ticket and how it is made of, as well as its workflow,
you will be able to manage every discussion in your CRM. Afterwards, we will explain individually the workflow of Campaign, Sale opportunity, Support Request and Meeting.
</p>
</details>
</section><section class="screenshot">
<h1>Example: Beta Developer Program</h1> <img title="Tickets example: Beta Developer Program" alt="Tickets example: Beta Developer Program" type="image/png" src="user-Tickets.Example.Beta.Developer.Program?format=png" /> <details open="open">
<p>
From the presentation of Events, we have had a general idea of how to use the CRM feature &quot;Event&quot; to manage company's interactions with external contacts. Following the VIFIB example, in the detail page of the <strong>Event</strong>
......@@ -85,8 +111,21 @@
Note that even a closed Ticket can be opened again.
</p>
<p>Now that the concept of a ticket is well understood, we will go in deep to the four specific tickets and their workflows in ERP5, which are Campaigns, Sale opportunities, Support requests and Meetings.</p> </details> </section><section class="screenshot">
<h1>Campaign: Beta Developer Program</h1> <img title="Campaign example: Beta Developer Program" alt="Campaign example: Beta Developer Program" type="image/png" src="user-Tickets.Campaign.Example.Beta.Developer.Program?format=png" /> <details open="open" /> </section><section class="illustration">
<h1>Campaign types</h1> <img title="Campaigns: Press release and Newsletter" alt="Campaigns: Press release and Newsletter" type="image/png" src="user-Tickets.Campaign.Press.Release.And.Newsletter?format=png" /> <details open="open">
<h1>Campaign: Beta Developer Program</h1> <img title="Campaign example: Beta Developer Program" alt="Campaign example: Beta Developer Program" type="image/png" src="user-Tickets.Campaign.Example.Beta.Developer.Program?format=png" />
<details open="open">
<p>
The first type of ticket we will discuss is a campaign. A campaign ticket is used to prepare a list of contact actions to be executed in the future and then track their execution.
Each contact action is defined as an event, assigned to staff. The list of events and their state track the progress of the campaign.
A campaign can be used to organise a programme for Beta developers of a software, to request proposals to different suppliers, to announce
a new product to press, etc.
</p>
<p>
We already had the example of the Beta developer program. We will follow this example.
</p>
</details>
</section><section class="illustration">
<h1>Campaign types</h1> <img title="Campaigns: Press release and Newsletter" alt="Campaigns: Press release and Newsletter" type="image/png" src="user-Tickets.Campaign.Press.Release.And.Newsletter?format=png" />
<details open="open">
<p> <strong>1. Press Release:</strong> </p>
<p>
Press Release is a Campaign starts from sending <strong>many different Events</strong>
......@@ -111,6 +150,8 @@
<strong>evaluation</strong>
of this campaign and the market prospects. These kinds of informations are very important if you want to be more efficient next time.
</p>
</details>
<details open="open">
<p> <strong>2. Newsletter:</strong> </p>
<p>
Newsletter is another kind of Campaign. The only difference with Press Release is that Newsletter starts from
......@@ -149,7 +190,7 @@
<h1>Sale Opportunity: VIFIB Offer PC Internet</h1> <img title="Sale Opportunity example: VIFIB Offer PC Internet" alt="Sale Opportunity example: VIFIB Offer PC Internet" type="image/png" src="user-Tickets.Sale.Opportunity.Example.VIFIB.Offer.PC.Internet?format=png" /> <details open="open">
<p>As you can see in the screen shot of the detail page of ticket Sale Opportunity &quot;VIFIB Offer PC Internet&quot;, in the case of a VIFIB offer in november 2011, we sent the promotion of PC through a newsletter to our customers. Some of them are interested in buying our products and services by replying to us saying &quot;Hello, I want more info about your products, I am interested in them.&quot; etc. From then on, we need to create a dedicate Ticket which will be a &quot;Sale Opportunity&quot;.</p> </details> </section><section class="illustration">
<h1>The role of Sale Opportunity</h1> <img title="Role of Sale Opportunity" alt="Role of Sale Opportunity" type="image/png" src="user-Tickets.Sale.Opportunity.Role?format=png" /> <details open="open">
<p>A sale opportunity starts from customers' replies which express their interest in our product and service. But normally few sale opportunity will come to a result very fast. First, only few clients will maybe take decisions fast. Second, there will be many actors involved in the decision to go with in the same sale opportunity: you might negotiate with the product supplier and the bank while keep in contact with your customers.</p>
<p>A sale opportunity starts from customers' replies which express their interests in our product and service. But normally few sale opportunities will come to a result very fast. First, only few clients will maybe take decisions fast. Second, there will be many actors involved in the decision to go with in the same sale opportunity: you might negotiate with the product supplier and the bank while keep in contact with your customers.</p>
<p>In one word, the decision from a sale opportunity can be made very quickly but sometimes it can take more than a year. So we need to use the Ticket &quot;Sale Opportunity&quot; to keep track of your commercial effort-your interactions with all the contacts involved, so to organise and to qualify our sale opportunities.</p> </details> </section><section class="illustration">
<h1>The workflow of a Sale Opportunity</h1> <img title="Sale Opportunity workflow" alt="Sale Opportunity workflow" src="user-Tickets.Sale.Opportunity.Workflow?format=png" type="image/png" /> <details open="open">
<p>
......@@ -158,7 +199,7 @@
<strong>created</strong>
the ticket Sale Opportunity to manage the following interactions between VIFIB, the customers, the PC supplier and the bank. She will
<strong>submitted</strong>
the Sale opportunity to the suppervisor. If Mr Smets the suppervisor verifies and approves the Sale opportunity, the operations manager and sales staff will
the Sale opportunity to the supervisor. If Mr Smets the supervisor verifies and approves the Sale opportunity, the operations manager and sales staff will
<strong>contact the prospect</strong>
and negotiate with the PC supplier. When sales condition is set, VIFIB will give the final
<strong>offer</strong>
......
......@@ -68,12 +68,13 @@
<value>
<tuple>
<string>publication_section/documentation/user</string>
<string>classification/collaborative/team</string>
<string>group/nexedi</string>
<string>contributor/person_module/796</string>
<string>contributor/person_module/590</string>
<string>classification/collaborative/team</string>
<string>contributor/person_module/2326</string>
<string>contributor/person_module/20111027-2BE16E4</string>
<string>group/nexedi</string>
<string>contributor/person_module/20130927-61A66CC</string>
</tuple>
</value>
</item>
......@@ -230,11 +231,13 @@
</item>
<item>
<key> <string>actor</string> </key>
<value> <string>supertristan</string> </value>
<value> <string>ni.yan</string> </value>
</item>
<item>
<key> <string>comment</string> </key>
<value> <string>touched for reconversion</string> </value>
<value>
<none/>
</value>
</item>
<item>
<key> <string>error_message</string> </key>
......@@ -242,7 +245,7 @@
</item>
<item>
<key> <string>serial</string> </key>
<value> <string>952.32900.30183.9228</string> </value>
<value> <string>952.61632.14481.43274</string> </value>
</item>
<item>
<key> <string>state</string> </key>
......@@ -260,7 +263,7 @@
</tuple>
<state>
<tuple>
<float>1468329817.88</float>
<float>1470042652.53</float>
<string>UTC</string>
</tuple>
</state>
......
......@@ -9,9 +9,9 @@
<h1>Add correction line to answer set</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.Add.Correction.Line.Action?format=png" /> <details open="true">To add correction line to the answer set as a whole, click on &quot;Add Correction Line&quot; under &quot;Action&quot; drop-down menu. Note: only use this action to add general evaluation to the whole answer set. To correct individual answer, use &quot;Fast Input&quot; action which is explained in the following sections of this tutorial.</details> </section><section class="screenshot">
<h1>Choose suitable correction</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.Add.Correction.Line?format=png" /> <details open="true">Choose the correction which fit your intend, then click on &quot;Set Relation&quot;.Then you will be redirected to the answer set page and the general corrections will be added.</details> </section><section class="screenshot">
<h1>Select the answer</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.Answer?format=png" /> <details open="true">Read the answers, and click on the answer that you want to correct.</details> </section><section class="screenshot">
<h1>Click on &quot;Fast Input&quot; at the answer page</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.FastInput?format=gif" /> <details open="true">Now you are located at the page of the answer line which you selected.To correct this answer, click on the button &quot;FastInput&quot; on the tool bar.</details> </section><section class="screenshot">
<h1>Choose the suitable correction</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.FastInput.Action?format=gif" /> <details open="true">Now you are directed to the correction line fast input page, choose the suitable corrections (could be multiple), then click on &quot;Add Correction Lines to Answer for Peer Review&quot;.</details> </section><section class="screenshot">
<h1>Add comment to the corrections</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.Add.Comment?format=gif" /> <details open="true">Now you are directed to the page to add comment. If you feel that the corrections were too general, you could add comment to the corrections which you choosed. Then, click on &quot;Explain Corrections&quot;.</details> </section><section class="screenshot">
<h1>Click on &quot;Fast Input&quot; at the answer page</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.FastInput?format=png" /> <details open="true">Now you are located at the page of the answer line which you selected.To correct this answer, click on the button &quot;FastInput&quot; on the tool bar.</details> </section><section class="screenshot">
<h1>Choose the suitable correction</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.FastInput.Action?format=png" /> <details open="true">Now you are directed to the correction line fast input page, choose the suitable corrections (could be multiple), then click on &quot;Add Correction Lines to Answer for Peer Review&quot;.</details> </section><section class="screenshot">
<h1>Add comment to the corrections</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.Add.Comment?format=png" /> <details open="true">Now you are directed to the page to add comment. If you feel that the corrections were too general, you could add comment to the corrections which you choosed. Then, click on &quot;Explain Corrections&quot;.</details> </section><section class="screenshot">
<h1>Continue with the next answer that need to be corrected</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.Next.Question?format=png" /> <details open="true">To continue with the corrections, you could click on the answer set title to go back to the overview of the answers, or click on &quot;next &quot; button on the tool bar to view the next answer.</details> </section><section class="screenshot">
<h1>Click on &quot;Request from Peer Review&quot; to request the answer set</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.Request.From.Peer.Review?format=png" /> <details open="true">After you finished correcting all the answers that need to be improved, save your changes, and click on &quot;Request from Peer Review&quot; under the &quot;Action&quot; menu.</details> </section><section class="screenshot">
<h1>Improve your own answer set after peer review</h1> <img type="image/svg+xml" src="http://img.erp5.cn/P-CLOUDIA-Configuration.Questionnaire.HowTo.Assign.Students.Peer.Reviewed.To.Improve?format=png" /> <details open="true">After the peer review process, you could view on the main page, under &quot;My Favourites&quot; menu, there is an option &quot;Peer Reviewed Answer Set to Improve&quot;. Click on this option, you could view and improve your own answer sets.</details> </section>
\ No newline at end of file
......@@ -242,11 +242,13 @@
</item>
<item>
<key> <string>actor</string> </key>
<value> <string>supertristan</string> </value>
<value> <string>klaus.woelfel</string> </value>
</item>
<item>
<key> <string>comment</string> </key>
<value> <string>touched for reconversion</string> </value>
<value>
<none/>
</value>
</item>
<item>
<key> <string>error_message</string> </key>
......@@ -272,7 +274,7 @@
</tuple>
<state>
<tuple>
<float>1468329830.07</float>
<float>1469112379.07</float>
<string>UTC</string>
</tuple>
</state>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment