FAQs for BAM

This page acts as a repository for frequently asked questions for the Blog Aggregation Management (BAM) project.

Current FAQs include:

Posts, marks and comments

Question

When markers’ comment and allocate a mark to a blog, who can see these comments and marks? Just the student?

Answer

There are two parts to this question, which is applicable depends on where the comment is being made:

  1. within BAM; or
    This is the most likely approach and more information is provided below.
  2. on the student’s blog.
    It is possible to comment on a student’s post by going to their blog and using the blog engine’s comment feature. If you use this approach, then the comment will normally be viewable by anyone, just like the student’s post. This is not normally how a marker would mark/comment on a post.

What follows only applies if you are using the BAM interface to mark and comment on the student’s post.

The short answer is that, only someone who logs into a CQU website using the student’s CQU username/password can see the comment and the mark. However, they can only see this, if the marked post has been released.

Currently, a post can only be released by David Jones.

Background: When a student makes a post to their blog, BAM creates a copy on a CQU server. It associates a “state” with the post. There are four possible states:

  1. UNALLOCATED – this means BAM was not able to match the post with one of the specified questions that students have to answer.
  2. Submitted – this means BAM could match it to one of the specified questions.
  3. Marked – this means a staff member has awarded a mark to the post.
  4. Released – in this state the mark and marker’s comments have been released so the student can see them. Before the post is in the “released” state, students cannot see the markers comments or mark.

This set of states is a close match to what is used in the CQU OASIS (assignment submission) system. It is designed to enable the course coordinator of moderator the option of moderating markers’ comments and marks before students can see them.

Not mirrored yet

Question

What does “Not mirrored yet” mean on the student blog details page?

Answer

Every couple of hours BAM checks the RSS feed of each student’s blog. If there have been any changes BAM creates an updated copy of the student’s blog on a university computer. i.e. it mirrors the student’s blog. (At this time BAM also checks the new posts to see if they are an answer to any of the required questions.

The “Student Blog Details” page of BAM manage (the first page you see when you login to BAM Manage) has a column “Last Post” that will show how long ago the student’s last post was mirrored by BAM. This is shown in days e.g. “4 days ago”.

Early in the term, this column may show “Not mirrored yet”. It means that BAM has not been able to make a local copy of the student blog yet. There are two main reasons why this might occur include:

  • The mirror process hasn’t been run since the student registered their blog.
    Solution: If you wait a couple of hours this should disappear when BAM next tried to mirror all student blogs.
  • There is some sort of problem that is preventing BAM from mirroring the student’s blog.
    Solution: You need to contact me so the problem can be diagnosed.

Is copy detection possible?

Question

Is it possible to run copy detection on the student blog posts?

Solution

Yes. It is fairly rudimentary and it is not automated, but it is possible.

Since it is currently not an automated process, let me know if you wish to have copy detection run. Please specify how often you would like it run (sorry, can’t do it more than once a week at this stage).

Limitations: currently the copy detection is only intra-corporal. i.e. it only checks student posts against other student posts. It doesn’t yet check against external sources. Technically this could be added (as could automation etc.), however, from a resource perspective this is not likely during the first half of 2009.

Leave a Reply

You must be logged in to post a comment.