Skip to Content
Last modified by Mathieu Jung-Muller on 2022/04/04 13:55
From version Icon 33.1 Icon
edited by Sneha Lodha
on 2022/04/02 15:42
Change comment: There is no comment for this version
To version Icon 10.1 Icon
edited by Mathieu Jung-Muller
on 2022/03/30 00:18
Change comment: There is no comment for this version

Summary

Details

Icon Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.snehalodha
1 +XWiki.Mathieu
Content
... ... @@ -1,22 +1,33 @@
1 -(% style="background-color:#ffffff; font-size:14px, text-align:center" %)
1 +(% style="background-color:#ffffff; font-size:14px" %)
2 2  
3 3  == IDP01==
4 +{{html}}
5 +<img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp1.jpg?rev=1.1" alt="IDP01" width="350"/>
6 +{{/html}}
4 4  
5 -[[image:idp1.jpg||width="400" height="350"]]
6 -
7 7  |(((
8 -**RANKING/ validation**
9 +**RANKING/ validation**
10 +
9 9  )))|(((
10 -When Pepper is playing music this can clearly be heard by the PwD, and other evaluators around, so this IDP is empirically testable.
12 +//Notion of the validity (e.g., empirically tested)//
13 +When Pepper is playing music this can clearly be heard by the PwD, and other evaluators around so this IDP is empirically testable.
14 +
11 11  )))
12 12  |(((
13 -**DESIGN PROBLEM (what)**
17 +**DESIGN PROBLEM (what)**
18 +
19 +
14 14  )))|(((
21 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
22 +
15 15  Here the interaction intention of the IDP is to gently remind/alert the PwD about the presence of Pepper around the room. This is in order not to startle the PwD by directly talking to them, but rather providing a gentle musical reminder of interaction about to take place. Sometimes the PwD might want to listen to some music for entertainment purposes and this IDP can also be applied in that scenario.
16 16  )))
17 17  |(((
18 18  **CONTEXT (use when…)**
27 +
28 +
19 19  )))|(((
30 +//Contextual characteristics that are significant for the applicability of the pattern.//
20 20  This IDP can be used in the following contexts:
21 21  * Alert the PwD before an interaction takes place
22 22  * Wake up reminder for PwD
... ... @@ -25,17 +25,34 @@
25 25  )))
26 26  |(((
27 27  **DESIGN SOLUTION (how)**
39 +
40 +
28 28  )))|(((
42 +//Essential characteristics of the design solution that express the interaction intention.//
43 +
29 29  This IDP contains minimal interaction, and only consists of Pepper playing music. The musical tone that will play in a specific scenario is pre-programmed for each activity. Hence the solution for gentle reminders for interaction about to happen for PwD, is to simply play some gentle reminder music.
30 30  In the case where this IDP is used for the entertainment of the PwD (external usecase), a list of songs that the PwD enjoys can be programmed into Pepper and played when the usecase is activated.
31 31  )))
32 32  |(((
33 33  **DESIGN RATIONALE (why)**
49 +
50 +
34 34  )))|(((
35 -According to many studies music has shown to have a dramatic effect on people with dementia in terms of improving recollection and making them feel more calm overall [1][2]. Due to these researches we decided to incorporate it not only for entertainment purposes, but also for some gentle reminder purposes.
52 +//Argumentation that resulted in the chosen design solution.//
53 +
54 +According to many studies music has shown to have a dramatic effect on people with dementia in terms of improving recollection and making them feel more calm overall. (Citations needed) Due to these researches we decided to incorporate it not only for entertainment purposes, but also for some gentle reminder purposes.
36 36  )))
56 +|(((
57 +**EXAMPLES (as seen on…)**
37 37  
59 +
60 +)))|(((
61 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
38 38  
63 +TBD (should we include or not?)
64 +)))
65 +
66 +
39 39  == IDP02==
40 40  {{html}}
41 41  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp2.jpg?rev=1.1" alt="IDP02" width="350"/>
... ... @@ -43,17 +43,29 @@
43 43  
44 44  |(((
45 45  **RANKING/ validation**
74 +
75 +
46 46  )))|(((
47 -This can be empirically tested as the PwD, and other evaluators around, can hear Pepper asking this question.
77 +//Notion of the validity (e.g., empirically tested)//
78 +This can be empirically tested as the PwD, and other evaluators around can hear Pepper asking this question.
79 +
48 48  )))
49 49  |(((
50 50  **DESIGN PROBLEM (what)**
83 +
84 +
51 51  )))|(((
86 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
87 +
52 52  It is important to understand whether the PwD did a particular task or not. Tasks such as taking medicine or eating a meal are crucial, and understanding whether the PwD has successfully done this is an important first step to many reminder tasks.
53 53  )))
54 54  |(((
55 -**CONTEXT (use when…)**
91 +**CONTEXT (use when…)**
92 +
93 +
56 56  )))|(((
95 +//Contextual characteristics that are significant for the applicability of the pattern.//
96 +
57 57  This IDP can be used in the following contexts:
58 58  * Understanding whether the PwD has taken medication before reminding them
59 59  * Understanding whether the PwD has eaten a meal before reminding them
... ... @@ -60,17 +60,36 @@
60 60  The list can be further expanded as more crucial task usecases are added.
61 61  )))
62 62  |(((
63 -**DESIGN SOLUTION (how)**
103 +**DESIGN SOLUTION (how)**
104 +
105 +
64 64  )))|(((
65 -The solution consists of explicitly asking the PwD whether they have already performed a particular task. The response from PwD can either be yes or no, and depending on that Pepper proceeds with the next step. Simply asking the PwD whether they have performed a task is the best way to ensure a clear and concise reply which is understandable.
107 +//Essential characteristics of the design solution that express the interaction intention.//
108 +
109 +The solution consists of explicitly asking the PwD whether they have already performed a particular task. The response from PwD can either be yes or no, and depending on that Pepper proceeds with the next step. Simply asking the PwD whether they have performed a task is the best way to ensure a clear and concise reply which is understandable.
110 +
66 66  )))
67 67  |(((
68 68  **DESIGN RATIONALE (why)**
114 +
115 +
69 69  )))|(((
117 +//Argumentation that resulted in the chosen design solution.//
118 +
70 70  Here instead of assessing from visual cues whether the PwD has conducted a particular task, a verbal approach is taken. This is due to Pepper's limitations in constantly being around the PwD. Although simply verbally asking whether the PwD performed a certain task might seem too straightforward, it ensures that important information is conveyed in the most explicit manner.
120 +
71 71  )))
122 +|(((
123 +**EXAMPLES (as seen on…)**
72 72  
125 +
126 +)))|(((
127 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
73 73  
129 +TBD (should we include or not?)
130 +)))
131 +
132 +
74 74  == IDP03==
75 75  {{html}}
76 76  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp3.jpg?rev=1.1" alt="IDP03" width="350"/>
... ... @@ -78,17 +78,29 @@
78 78  
79 79  |(((
80 80  **RANKING/ validation**
140 +
141 +
81 81  )))|(((
82 -This can be empirically tested as the PwD, and other evaluators around, can hear Pepper reminding the PwD to do the task.
143 +//Notion of the validity (e.g., empirically tested)//
144 +This can be empirically tested as the PwD, and other evaluators around can hear Pepper reminding the PwD to do the task.
145 +
83 83  )))
84 84  |(((
85 -**DESIGN PROBLEM (what)**
148 +**DESIGN PROBLEM (what)**
149 +
150 +
86 86  )))|(((
152 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
153 +
87 87  The idea of this design pattern is to verbally remind the PwD of an upcoming task. Such tasks can include medicine reminders, meal reminders etc. The intended effect on the user would be that they are reminded to do this particular task if they have not done it already. It also takes some of the burden away from primary caregivers and partners to do such a reminding job constantly.
88 88  )))
89 89  |(((
90 90  **CONTEXT (use when…)**
158 +
159 +
91 91  )))|(((
161 +//Contextual characteristics that are significant for the applicability of the pattern.//
162 +
92 92  This IDP can be used in the following contexts:
93 93  * Reminding the PwD to take medication if they have not done so already
94 94  * Reminding the PwD to eat food if they have not done so already
... ... @@ -96,16 +96,32 @@
96 96  )))
97 97  |(((
98 98  **DESIGN SOLUTION (how)**
170 +
171 +
99 99  )))|(((
100 -The design solution consists of Pepper reminding the PwD to do a particular task if they have not done it already. We ensure this reminder is only activated when the PwD has not performed the task in order not to overwhelm them with something they have already done. The goal of the pattern is to successfully remind and encourage the PwD to perform an essential task they should do.
173 +//Essential characteristics of the design solution that express the interaction intention.//
174 +
175 +The design solution consists of Pepper reminding the PwD to do a particular task if they have not done it already. We ensure this reminder is only activated when the PwD has not performed the task in order not overwhelm them with something they have already done. The goal of the pattern is to successfully remind and encourage the PwD to perform an essential task they should do.
101 101  )))
102 102  |(((
103 103  **DESIGN RATIONALE (why)**
179 +
180 +
104 104  )))|(((
105 -A verbal reminder here works better than a simple reminder on the phone, as would happen commonly these days. Also we believe that having Pepper as a physical being there might encourage the PwD to take such reminders with higher importance than a simple notification. On top of that, phone reminders would mean that the PwD is familiar with this kind of technology, which is not necessarily the case.
182 +//Argumentation that resulted in the chosen design solution.//
183 +A verbal reminder here works better than a simple reminder on the phone, as would happen commonly these days. Also we believe that having Pepper's as a physical being there might encourage the PwD to take such reminders with higher importance than a simple notification.
184 +
106 106  )))
186 +|(((
187 +**EXAMPLES (as seen on…)**
107 107  
189 +)))|(((
190 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
108 108  
192 +TBD (should we include or not?)
193 +)))
194 +
195 +
109 109  == IDP04==
110 110  {{html}}
111 111  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp4.jpg?rev=1.1" alt="IDP04" width="350"/>
... ... @@ -113,17 +113,29 @@
113 113  
114 114  |(((
115 115  **RANKING/ validation**
203 +
204 +
116 116  )))|(((
117 -This can be empirically tested as the PwD, and other evaluators around, can hear Pepper asking the PwD for confirmation.
206 +//Notion of the validity (e.g., empirically tested)//
207 +This can be empirically tested as the PwD, and other evaluators around can hear Pepper asking the PwD for confirmation.
208 +
118 118  )))
119 119  |(((
120 120  **DESIGN PROBLEM (what)**
212 +
213 +
121 121  )))|(((
215 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
216 +
122 122  This design pattern occurs hand in hand with Pepper just having told the PwD to do a certain task or activity step. The intention is to understand whether this task was successfully done by the PwD. This ensures the PwD had indeed successfully completed a certain task, which in some case may be crucial.
123 123  )))
124 124  |(((
220 +
125 125  **CONTEXT (use when…)**
222 +
126 126  )))|(((
224 +//Contextual characteristics that are significant for the applicability of the pattern.//
225 +
127 127  This IDP can be used in the following contexts:
128 128  * Asking for confirmation of having taken medication
129 129  * Asking for confirmation of having eaten a meal
... ... @@ -132,16 +132,33 @@
132 132  )))
133 133  |(((
134 134  **DESIGN SOLUTION (how)**
234 +
235 +
135 135  )))|(((
237 +//Essential characteristics of the design solution that express the interaction intention.//
238 +
136 136  The design solution consists of Pepper asking for a verbal confirmation of having done a task. The user is prompted with a closed question such as "have you done it?," and is expected to reply in a truthful manner. Pepper will not move on unless a positive confirmation is given, in order to ensure successful completion of crucial tasks.
137 137  )))
138 138  |(((
139 139  **DESIGN RATIONALE (why)**
243 +
244 +
140 140  )))|(((
141 -The solution consists of explicitly asking the PwD whether they have already performed a particular task. The response from PwD can either be positive or negative, and depending on that Pepper proceeds with the next step. Simply asking the PwD whether they have performed a task is the best way to ensure a clear and concise reply which is understandable.
246 +//Argumentation that resulted in the chosen design solution.//
247 +
248 +The solution consists of explicitly asking the PwD whether they have already performed a particular task. The response from PwD can either be yes or no, and depending on that Pepper proceeds with the next step. Simply asking the PwD whether they have performed a task is the best way to ensure a clear and concise reply which is understandable.
249 +
142 142  )))
251 +|(((
252 +**EXAMPLES (as seen on…)**
143 143  
254 +)))|(((
255 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
144 144  
257 +TBD (should we include or not?)
258 +)))
259 +
260 +
145 145  == IDP05==
146 146  {{html}}
147 147  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp5.jpg?rev=1.1" alt="IDP05" width="350"/>
... ... @@ -148,18 +148,29 @@
148 148  {{/html}}
149 149  
150 150  |(((
151 -**RANKING/ validation**
267 +**RANKING/ validation**
268 +
269 +
152 152  )))|(((
153 -This can be empirically tested as the PwD, and other evaluators around, can hear Pepper congratulating the PwD.
271 +//Notion of the validity (e.g., empirically tested)//
272 +This can be empirically tested as the PwD, and other evaluators around can hear Pepper congratulating the PwD.
154 154  )))
155 155  |(((
156 156  **DESIGN PROBLEM (what)**
276 +
277 +
157 157  )))|(((
158 -This design pattern is used to verbally congratulate the PwD, and make them feel about about a task that they just accomplished. This is to lift the spirits of the PwD and make them enjoy and want to do certain tasks.
279 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
280 +
281 +This design pattern is used to verbally congratulate the PwD, and make the feel about about a task that they just accomplished. This is to lift the spirits of the PwD and make the enjoy and want to do certain tasks.
159 159  )))
160 160  |(((
284 +
161 161  **CONTEXT (use when…)**
286 +
162 162  )))|(((
288 +//Contextual characteristics that are significant for the applicability of the pattern.//
289 +
163 163  This IDP can be used in the following contexts:
164 164  * Congratulate the PwD for having taken medication
165 165  * Congratulate the PwD for having eaten medication
... ... @@ -168,17 +168,32 @@
168 168  )))
169 169  |(((
170 170  **DESIGN SOLUTION (how)**
298 +
299 +
171 171  )))|(((
301 +//Essential characteristics of the design solution that express the interaction intention.//
302 +
172 172  This IDP is quite basic and simply pre-programmed into Pepper. Simply congratulating the PwD for finishing a certain task or activity is sufficient.
173 173  )))
174 174  |(((
175 175  **DESIGN RATIONALE (why)**
307 +
308 +
176 176  )))|(((
177 177  //Argumentation that resulted in the chosen design solution.//
178 -This IDP was added in order to give the PwD a feeling of accomplishment after doing a task that might have been challenging for them. Giving some encouragement can aid in finding enjoyment in and remembering such tasks.
311 + This IDP was added in order to give the PwD a feeling of accomplishment after doing a task that might have been challenging for them. Giving some encouragement can aid in finding enjoyment in and remembering such tasks.
312 +
179 179  )))
314 +|(((
315 +**EXAMPLES (as seen on…)**
180 180  
317 +)))|(((
318 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
181 181  
320 +TBD (should we include or not?)
321 +)))
322 +
323 +
182 182  == IDP06==
183 183  {{html}}
184 184  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp6.jpg?rev=1.1" alt="IDP06s" width="350"/>
... ... @@ -186,17 +186,28 @@
186 186  
187 187  |(((
188 188  **RANKING/ validation**
331 +
332 +
189 189  )))|(((
190 -This can be tested by performing some other IDPs, which refer to utilizing the breakdown of a particular activity. Since this is for now hard-coded into Pepper, it is not empirically testable.
334 +//Notion of the validity (e.g., empirically tested)//
335 +This can be tested by performing some other IDPs, which refer to utilizing the breakdown of a particular activity. Since this some programmed into Pepper, it is not empirically testable.
191 191  )))
192 192  |(((
193 193  **DESIGN PROBLEM (what)**
339 +
340 +
194 194  )))|(((
195 -This design pattern is used by the HCP (or a relative) to enter some activities into Pepper, that the PwD might personally enjoy. This is so that Pepper's system contains the breakdown to certain desired activities.
342 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
343 +
344 +This design pattern is used by the HPC inorder to enter some activities into Pepper, that that the PwD might personally enjoy. This is so that Pepper's system contains the breakdown to certain desired activities.
196 196  )))
197 197  |(((
347 +
198 198  **CONTEXT (use when…)**
349 +
199 199  )))|(((
351 +//Contextual characteristics that are significant for the applicability of the pattern.//
352 +
200 200  This IDP can be used in the following contexts:
201 201  * PwD wants to perform a new activity
202 202  * Pepper is not yet personalized to the particular PwD
... ... @@ -203,16 +203,32 @@
203 203  )))
204 204  |(((
205 205  **DESIGN SOLUTION (how)**
359 +
360 +
206 206  )))|(((
207 -The interface has not been implemented. Ideally, the interface designed is easy to use, HCP and relatives are not required to have very high technical knowledge.
362 +//Essential characteristics of the design solution that express the interaction intention.//
363 +
364 +Here in order to easy configuration of Pepper, we will utilize the tablet feature where the HPC can enter activity steps. This is so that the caregiver also has some autonomy over Pepper rather than just the developers. The interface designed is easy to use as, HCPs are not required to have very high technical knowledge.
208 208  )))
209 209  |(((
210 210  **DESIGN RATIONALE (why)**
368 +
369 +
211 211  )))|(((
212 -We allow the HCP to provide steps as they are the ones that have spent a significant amount of time with the PwD and know about their likes and dislikes. In this case, they can also provide the steps in the complexity they think the PwD will understand, rather than simply having some arbitrary steps from the internet.
371 +//Argumentation that resulted in the chosen design solution.//
372 +We allow the HPC to provide steps has they are they ones that have spent a significant amount of time with the PwD and know about their likes and dislikes. In this case they can also provide the steps in the complexity they think the PwD will understand, rather than having some arbitrary step up of steps from the internet.
373 +
213 213  )))
375 +|(((
376 +**EXAMPLES (as seen on…)**
214 214  
378 +)))|(((
379 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
215 215  
381 +TBD (should we include or not?)
382 +)))
383 +
384 +
216 216  == IDP07==
217 217  {{html}}
218 218  <img src="https://xwiki.ewi.tudelft.nl/xwiki/wiki/sce2022group04/download/Main/WebHome/idp7.jpg?rev=1.1" alt="IDP07" width="350"/>
... ... @@ -220,17 +220,29 @@
220 220  
221 221  |(((
222 222  **RANKING/ validation**
392 +
393 +
223 223  )))|(((
224 -This can be empirically tested as the PwD, and other evaluators around, can hear Pepper saying a step to the PwD.
395 +//Notion of the validity (e.g., empirically tested)//
396 +This can be empirically tested as the PwD, and other evaluators around can hear Pepper saying a step to the PwD.
397 +
225 225  )))
226 226  |(((
227 227  **DESIGN PROBLEM (what)**
401 +
402 +
228 228  )))|(((
404 +//Concise description of the intended interaction (effect on the user and/or user interaction with the system and/or other parties).//
405 +
229 229  This design pattern is used to tell the PwD the next step in a certain activity breakdown. This activity can be anything, and the steps are added by the HCP into Pepper's system as a prerequisite.
230 230  )))
231 231  |(((
409 +
232 232  **CONTEXT (use when…)**
411 +
233 233  )))|(((
413 +//Contextual characteristics that are significant for the applicability of the pattern.//
414 +
234 234  This IDP can be used in the following contexts:
235 235  * PwD needs the next step for a gardening activity
236 236  * PwD needs the next step for making a paper plane
... ... @@ -237,15 +237,27 @@
237 237  )))
238 238  |(((
239 239  **DESIGN SOLUTION (how)**
421 +
422 +
240 240  )))|(((
241 -Here, already having the activity broken down into certain steps is very crucial. Also Pepper needs to say these steps verbally so the user can hear and act appropriately.
424 +//Essential characteristics of the design solution that express the interaction intention.//
425 +Here already having the activity broken down into certain steps is very crucial. Also Pepper needs to stay these steps verbally so the user can hear and act appropriately.
242 242  )))
243 243  |(((
244 244  **DESIGN RATIONALE (why)**
429 +
430 +
245 245  )))|(((
246 -A verbal step here works better than merely following steps from a website, as would happen commonly these days. Also we believe that having Pepper as a physical being there might encourage the PwD to perform activities they used to enjoy, with higher frequency as Pepper would come up to them and ask them if they want to take part in an activity they enjoy.
432 +//Argumentation that resulted in the chosen design solution.//
433 +A verbal step here works better than a simply following steps from a website, as would happen commonly these days. Also we believe that having Pepper's as a physical being there might encourage the PwD to perform activities they used to enjoy with higher frequency as Pepper would come up to them and ask them in they want to take part in an activity they enjoy.
247 247  )))
435 +|(((
436 +**EXAMPLES (as seen on…)**
248 248  
438 +)))|(((
439 +//Illustration (eg. picture, screenshot, animated graphic, video etc.) of an implementation of the design solution in a ‘real-life’ application, and include a short explanation describing the context of use.//
249 249  
250 -[1] Baird, A., & Samson, S. (2015). Music and dementia. Progress in brain research, 217, 207-235. https://www.cochranelibrary.com/cdsr/doi/10.1002/14651858.CD003477.pub2/abstract.
251 -[2] McDermott, O., Orrell, M., & Ridder, H. M. (2014). The importance of music for people with dementia: the perspectives of people with dementia, family carers, staff and music therapists. Aging & mental health, 18(6), 706-716. https://www.tandfonline.com/doi/full/10.1080/13607863.2013.875124
441 +TBD (should we include or not?)
442 +)))
443 +
444 +
Icon idp1.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content Icon
Icon idp2.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -86.2 KB
Content Icon
Icon idp3.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -90.9 KB
Content Icon
Icon idp4.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -84.4 KB
Content Icon
Icon idp5.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -88.5 KB
Content Icon
Icon idp6.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -91.1 KB
Content Icon
Icon idp7.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.snehalodha
Size
... ... @@ -1,1 +1,0 @@
1 -88.5 KB
Content Icon