Comprehensive exam in moodle - moodle

I need to build a Comprehensive Exam which is build of three main title and 10 Question in each title.
Is it possible to simulate a comprehensive exam with moodle?

Do you mean this: http://en.wikipedia.org/wiki/Comprehensive_examination ?
The article notes that 'There is no standard definition for what such exams entail', so I would suggest that the answer is 'Yes', but it will depend on exactly what you are trying to achieve. The quiz module within Moodle is quite capable of creating a 3 page quiz, with 10 questions on each page (or it can be more than 3 pages, with some static text defining the break between the sections).
If, however, you are wanting to have separate grades for each of the sections, then you would probably have to split it across 3 quizzes (possibly using conditional availability to prevent access to the second & third quizzes until the first has been answered).

Related

R/exams: Open-ended questions with exams2moodle

My goal is to create a question using R/exams and Moodle including a few plots generated in the Rmd exercise file. The students should describe the plots verbally and then the exercise is graded manually.
Is it possible to use exams2moodle to create such an open-ended free text question for Moodle? There is no extype for it. In the documentation the only hint is:
"In order to generate free text questions in moodle one may specify extra parameters via \exextra. Currently the following options are supported:".
I have tried to add \exextra parameters to the metainformation, but it did not change anything.
A worked example can be found in the essayreg exercise shipped within the package, see: http://www.R-exams.org/templates/essayreg/
And you are right that this is not very well documented. The reason is that we have used somewhat different exextra tags for the Moodle export and for the QTI 2.1 export. We habe to improve and unify that in one of the next R/exams versions.
Also, another pointer, in case this is useful to anyone reading the question: Another useful strategy for asking about the interpretation of (statistical) graphics is in multiple-choice format. Let the participants judge some statements about the graphic that can either be approximately correct or clearly wrong. Of course, with open-ended question you can catch more nuances but with multiple-choice questions you can automatically assess a much larger number of participants. Or participants can self-assess in practice quizzes etc. Examples for this are the boxplots and scatterplot exercises:
http://www.R-exams.org/templates/boxplots/
http://www.R-exams.org/templates/scatterplot/

Creating custom daily evalutations in Moodle

I've been looking for a solution for kindergarten teachers to submit daily student evaluations (different criteria) in Moodle. So far, the closest solution that I've found is the Attendance plugin.
Does anyone know of a plugin that allows the teacher to submit a daily evaluation?
Another option that I'm looking into is Moodle Competency, which can actually fit the need, however, it looks like competency is not cumulative ... if I can find a way to make it cumulative that will be awesome.
For example, one of the competencies we have is "able to read sentences" and the scale is "1 - non-developed", "2- being developed" and "3- fully developed". At any point, the teacher or school admin would like to know how competent the student is. In our case, if this is an indicator that is being responded daily, we should be able to take the average and be able to evaluate the student.
The competency framework (to my understanding) doesn't calculate the average, rather it relies on being rated by the teacher.
Any thoughts where I should continue to look?
Attendance could be a great solution to your needs.
It could be hidden to the ones acting like students (I'm not shure if the kindergarden kids be interested in see this, maybe their parents)
Attendance have a full compatibility with course grading.
It could be configured to have diferent percentaje of final grading, so far, you can use one attendance activity for have a registry for their personal clairliness, another to record assessment in math, one more to social assessment and so on.
Finally all users with minimun acces as teacher (or another role you defined: example: school administration, scholar control) Could have facilities to export every grading to spreadsheet.
I've several years using it in a similar way you are asking to.
I hope this helps you.

In MS-Access, can you Save multiple forms into 1 PDF

I am creating a database in MS-Access to manage product specifications. Some products have overlapping specifications and some are unique.
My initial approach to this problem was to create multiple forms. For Example: an extension cord specification needs copper, compound and plug information. This information is also needed for a power strip specification, as well as other information that is ONLY pertinent to power strips. Currently I have created multiple forms for the different products. Is it possible to save multiple forms into a pdf for the same part number?
I know I can create a long form that is split on different pages, this method could work if I could not save or print certain pages depending on the product too. Any help is greatly appreciated.
I have shown in the picture below a portion of the forms and how some information is relevant only to the product class.
I know I could create forms for a basis of every category of inventory, but then I would have to create a full specification form for over 10 products, I am trying to streamline and reduce the amount of front end work required to generate specs from our database

MongoDB model design for meteorjs app

I'm more used to a relational database and am having a hard time thinking about how to design my database in mongoDB, and am even more unclear when taking into account some of the special considerations of database design for meteorjs, where I understand you often prefer separate collections over embedded documents/data in order to make better use of some of the benefits you get from collections.
Let's say I want to track students progress in high school. They need to complete certain required classes each school year in order to progress to the next year (freshman, sophomore, junior, senior), and they can also complete some electives. I need to track when the students complete each requirement or elective. And the requirements may change slightly from year to year, but I need to remember for example that Johnny completed all of the freshman requirements as they existed two years ago.
So I have:
Students
Requirements
Electives
Grades (frosh, etc.)
Years
Mostly, I'm trying to think about how to set up the requirements. In a relational DB, I'd have a table of requirements, with className, grade, and year, and a table of student_requirements, that tracks the students as they complete each requirement. But I'm thinking in MongoDB/meteorjs, I'd have a model for each grade/level that gets stored with a studentID and initially instantiates with false values for each requirement, like:
{
student: [studentID],
class: 'freshman'
year: 2014,
requirements: {
class1: false,
class2: false
}
}
and as the student completes a requirement, it updates like:
{
student: [studentID],
class: 'freshman'
year: 2014,
requirements: {
class1: false,
class2: [completionDateTime]
}
}
So in this way, each student will collect four Requirements documents, which are somewhat dictated by their initial instantiation values. And instead of the actual requirements for each grade/year living in the database, they would essentially live in the code itself.
Some of the actions I would like to be able to support are marking off requirements across a set of students at one time, and showing a grid of users/requirements to see who needs what.
Does this sound reasonable? Or is there a better way to approach this? I'm pretty early in this application and am hoping to avoid painting myself into a corner. Any help suggestion is appreciated. Thanks! :-)
Currently I'm thinking about my application data design too. I've read the examples in the MongoDB manual
look up MongoDB manual data model design - docs.mongodb.org/manual/core/data-model-design/
and here -> MongoDB manual one to one relationship - docs.mongodb.org/manual/tutorial/model-embedded-one-to-one-relationships-between-documents/
(sorry I can't post more than one link at the moment in an answer)
They say:
In general, use embedded data models when:
you have “contains” relationships between entities.
you have one-to-many relationships between entities. In these relationships the “many” or child documents always appear with or are viewed in the context of the “one” or parent documents.
The normalized approach uses a reference in a document, to another document. Just like in the Meteor.js book. They create a web app which shows posts, and each post has a set of comments. They use two collections, the posts and the comments. When adding a comment it's submitted together with the post_id.
So in your example you have a students collection. And each student has to fulfill requirements? And each student has his own requirements like a post has his own comments?
Then I would handle it like they did in the book. With two collections. I think that should be the normalized approach, not the embedded.
I'm a little confused myself, so maybe you can tell me, if my answer makes sense.
Maybe you can help me too? I'm trying to make a app that manages a flea market.
Users of the app create events.
The creator of the event invites users to be cashiers for that event.
Users create lists of stuff they want to sell. Max. number of lists/sellers per event. Max. number of position on a list (25/50).
Cashiers type in the positions of those lists at the event, to track what is sold.
Event creators make billings for the sold stuff of each list, to hand out the money afterwards.
I'm confused how to set up the data design. I need Events and Lists. Do I use the normalized approach, or the embedded one?
Edit:
After reading percona.com/blog/2013/08/01/schema-design-in-mongodb-vs-schema-design-in-mysql/ I found following advice:
If you read people information 99% of the time, having 2 separate collections can be a good solution: it avoids keeping in memory data is almost never used (passport information) and when you need to have all information for a given person, it may be acceptable to do the join in the application.
Same thing if you want to display the name of people on one screen and the passport information on another screen.
But if you want to display all information for a given person, storing everything in the same collection (with embedding or with a flat structure) is likely to be the best solution

word suggestion based on input algorithm?

I am thinking of creating a web site, which lets people to rate restaurants. Since I don't have a database containing all the restaurants, this web site relies on user's inputs.
But there is a problem of this method, because people may use different word (name) to describe a same restaurant, but I don't want to create different entries inside the database, as they refer to the same restaurant.
For example, when describing KFC, somebody use the name "KFC", others may use "Kentucky Fried Chicken"
How can I make the system to automatically detect this? and give the user a list of existing items of the database.
This should quite similar to stackoverflow, which tells you "questions with similar title". But I don't know how to implement this.
You can't ... you have to create a list of the restaurant names and their "synonyms" and other possible spellings.
How can I make the system to automatically detect this?
The system doesn't know that "KFC" means "Kentucky Fried Chicken".
Make a map of synonyms, to let it know.
This should quite similar to stackoverflow, which tells you "questions with similar title"
It generally matches word-for-word. It may have an internal list of synonyms to deal with common cases.