At the BAAA.dk all reports are handed in online via Wiseflow and they’re saved in a Office365 database. Above is the result if I search the word WordPress. Since the system is relatively the numbers don’t mean much … yet.
For this research project this is a most valuable source. From the reports we can see how WordPress is used by businesses and students.
https://make.wordpress.org/core/2016/10/07/twenty-seventeen-meeting-notes-oct-7-2016/ Agenda and sum up from the meeting.
Of special interest is this discussion on costum colors.
If your method is waterfall, you’d have phases like:
But in Twentyseventeen there was a theme, it was forked and two weeks before launch color options are discussed. The method is clearly iterative. Problems are solves when they arise.
Videos and animated gifs are used for visualization of ideas. Interesting process indeed.
Tomboy is not the best project manager on earth. I decided to use Trello as my kanban. It’s very basic:
Since you can link from Trello to Google Docs I made online versions of the project description and a sheet for the overall plan.
I suggested, that a closing div should have a comment. David A. Kennedy did the job. Here’s the code and change.
Here’s the updated code on Github.
But: how do you contribute with code as opposed to suggestions?
I found out that a URL field would be nice. So here’s the new and improved research database schema. During research I often meet online sources. In this way they are stored in one place.
Originally the database was an implementation of the “Liza Matrix” (named after Dr. Liza Castro’s talk on literature reviews). The original matrix was suited for a spreadsheet. But spreadsheets are not suited for notes.
I’ll name the fork “Per’s Review Schema“. Perhaps a timestamp would come in handy in the lit_noter table. That would open up for “visited the xxxx-xx-xx” type of output.
A JOIN of all rows was added. So the database is ready for queries.
select `litrev`.`lit_id` AS `lit_id`,`litrev`.`titel` AS `titel`,`litrev`.`forfatter` AS `forfatter`,`litrev`.`tidsskrift` AS `tidsskrift`,`litrev`.`udgiver` AS `udgiver`,`litrev`.`anno` AS `anno`,`litrev`.`researchsp` AS `researchsp`,`litrev`.`teorigrundlag` AS `teorigrundlag`,`litrev`.`metode` AS `metode`,`litrev`.`relevans` AS `relevans`,`litrev`.`anbefalinger` AS `anbefalinger`,`litrev`.`konklusion` AS `konklusion`,`litrev`.`url_projekt` AS `url_projekt`,`litrev`.`when` AS `when`,`lit_noter`.`lit_noter_id` AS `lit_noter_id`,`lit_noter`.`litrev_id` AS `litrev_id`,`lit_noter`.`side` AS `side`,`lit_noter`.`notat` AS `notat` from (`litrev` left join `lit_noter` on((`litrev`.`lit_id` = `lit_noter`.`litrev_id`)))
Read three reports today- I’m using the database for notes on cases. I wish access to more cases. On the other hand the literature review is somewhat time consuming. After 10 – 15 cases I guess that I’ll get the overall picture. Since I’m looking for qualitative rather than quantitative data it’s kinda ok-ish.
Andrew Abela: Extreme Presentations.
See Mark Jaquith‘s toolbox.
Seems like the answer is:
In a similar manner you can create tickets too.
At this point the developers of Twentyseventeen will focus on costum usability for the website maintainers. A ticket on developing costumize panels bykarmatosed is here.
The game is afoot.
We use cookies - more information
Multimusen.dk will set a few cookies from Doubleclick, Google and the Social Media plugins they ay set some cookies. Some of my pages use APIs - such as YouTube, LinkedIn, Google Fonts, Google Maps, Mapbox, Spotify, Jetpack, Twitter, Facebook &c.. Such plugins may set the odd cookie.
