Development follow up

April 22nd, 2015

Things are going well! You can see the Project Description Template in action here :

Both projects look the same. The difference is that one have a few less Semantic properties. I made the Affiliated University / Institution text disappear when not used, because it would be very normal that a project would not be affiliated with one of these.

In order to understand the development orientations, I invite you to read the Template Description page, along all the Semantic properties pages (see Project Description Test 1 facts box in the bottom of the page for a link for each properties.

Note : I saw there are Templates description Templates used in Appropedia, although using sub pages for this is new to me. I need a little help getting me started and then I will normalize my Template and Semantic Properties documentation.

Next steps would be :

  • Associate the Category:Projects with Form:Project Description, adding the semantic property [[Has default form::Project Description]] to the Category page.
  • Develop MediaWiki:Project Description form preload, as MediaWiki:Medical Device form preload; Lonny or Chris, I will need you to create the page when I'm done because it is in Mediawiki: Namespace and I am not allowed to write there. There is also some kind of autofill to pages created with the Form Edit field in the Projects Category page. We could probably use this?
  • Create EWB Challenge Project generic page, with queries on the EWB Challenge Project Project type
  • Automatically set the Category Projects to the pages created with the form, as well as the EWB Challenge Project Category to the ones with this type. It will look like this : Sanitation and [[Category:Sanitation]]
  • Review other details from the Appropedia:EWB Challenge site development/Structure page.


Thanks Guillaume, this looks great!
  • "I saw there are Templates description Templates used in Appropedia, although using sub pages for this is new to me."
  • This would be the work of some Wikipedian editors, copying the way they do it there. You do not need to do this - I usually don't do it, and Lonny and I find it a bit confusing too. So I think it's okay to do the simplest thing that works :-).
  • You are now an admin and can edit the "MediaWiki" namespace.
  • In Project Description Test 1, there is no option to edit with form. Lonny & I don't know why that happens. E.g. see IStethoscope, there is "edit" (which is edit with form) and "edit source".
  • Can we add a photo like it is in the medical devices?
  • Let's change:
    • "Project Type" to "Affiliation"
    • "Affiliated University/Institution" to "Host University/Institution". (We can choose the exact wording later. "Host University/School/Institution/Program" seems too long. "Host Institution/Program"?)
  • Re Status: I *think* this could be a radio style input, but we have asked for confirmation from Pr Joshua Pearce (the major user of status tags). We'll let you know. --Chriswaterguy (talk) 18:42, 22 April 2015 (PDT)

April 20th, 2015

--Guillaume Coulombe (talk) 14:24, 20 April 2015 (PDT)


April 15, 2015

It did start the prototyping of the semantics for EWB Projects in Appropedia. I did these developments on a wiki on my side. The look is a bit different, but the wiki code will be pretty much the same. It is only the <div> encodings that could change a bit. Nothing that make us work more.

I would like input on 2 questions :

  1. Please give me your preference for the Look and feel of the Form: I did develop 2 models, one that is more Questionnaire style, one that is more Table type. Which one do you prefer? My favorite is the Questionnaire, but may be you want something more succint. Note : I'm still at prototype : English will get better ;-) - as well, data fields will be activated with the creation of the Semantic Properties pages, which I will only do on Appropedia site : this is why the answers are in redlink and the form reacting a bit so-so.
  2. On another hand, if you look at the semantic properties listed in this page, It is feasible to treat the Model to develop as something a bit more generic than EWB. Of course, I do not suggest to do a global project management ontology, but to treat EWB Challenge project as a Project Type. This way, with this Example page, instead of writing in the Model EWB Challenge Project, I would put the semantic property "Has type" in the header and EWB Challenge Project would appear as well. As for the other properties, they could be quite generic, as Affiliated University would be my suggestion for EWB Challenge University, which is something that happens in different project. That way, we could query different or unique Types of project, to filter all projects affiliated with an institution, or only the EWB Challenge Project. My suggestion is to go generic, as it will be more flexible and adaptative and easier to put a form for a generic category than just a specific.

--Guillaume Coulombe (talk) 12:41, 15 April 2015 (PDT)

Thanks Guillaume, this looks good.
Re the 2 models, I like both.
I think your idea (treating EWB Challenge project as a Project Type) makes good sense.
That's my initial impression - I will look in more detail later at the required fields/data. Thank you! --Chriswaterguy (talk) 19:54, 15 April 2015 (PDT)
Cookies help us deliver our services. By using our services, you agree to our use of cookies.