Online Journal / e-Portfolio
Hello, I need a way to make it easier for users to create an on-line portfolio of their work (the users are students doing school projects). The way we've been doing it so far is that they just make regular HTML pages. This means that the pupil must be mindful to keep an index page or else it'll be impossible to find their work scattered all over the site. I would love to have something that kept a group of pages together. I looked at the "book" content type and I liked it, BUT anyone can insert a page in anyone else's book. That's not what we want. We also don't want each user to be faced with a list of 2,000 "books" to choose from when Drupal asks to which book they want to add their page. Can anyone think of a better alternative? I took a look at the E-Journal module and that didn't do what I wanted either. E-Journal is to create a regular publication with issues and volumes and the like. Using a Blog would normally be a possibility, except that one of their projects that involves keeping a blog to record their progress. Any ideas? Thanks for the help. Daniel.
Quoting Daniel Carrera <daniel.carrera@zmsl.com>:
Can anyone think of a better alternative?
http://drupal.org/project/og And associated modules http://drupal.org/project/Modules/category/90 Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/
Hi - I am trying to target a new content type in my node template so as not to show certain items. Normally I use the node id which works fine but now i want to blanket a node type. Here is what I am uisng in my query: $content_type=="mootype" full string: if (arg(1)=="862" || arg(1)=="3" || arg(1)=="56" || arg(1)=="76" || arg(1)=="245" || arg(1)=="5" || arg(1)=="1711" || $content_type=="mootype") But it's not taking it - any ideas? Thanks, Allen
Earnie Boyd wrote:
Can anyone think of a better alternative?
And associated modules http://drupal.org/project/Modules/category/90
I just installed some of those and took a look. It looks like it's designed to make groups of *users* with subscription and stuff like that. The biggest problem is that when you create a page the user sees a checkbox for every "audience" in the system. If each student has a "group" for their online portfolio we could end up with a thousand checkboxes :-P Daniel.
Daniel Carrera wrote:
Earnie Boyd wrote:
Can anyone think of a better alternative?
And associated modules http://drupal.org/project/Modules/category/90
I just installed some of those and took a look. It looks like it's designed to make groups of *users* with subscription and stuff like that. The biggest problem is that when you create a page the user sees a checkbox for every "audience" in the system. If each student has a "group" for their online portfolio we could end up with a thousand checkboxes :-P
Daniel.
In the "Node authoring form" section of the Organic Groups configuration, there is an "Audience checkboxes" option that might take care of your concern: "Show each subscribed group as a checkbox in the Audience section. This enables user to place her post into multiple groups. If unchecked, simplify the user interface by omitting the checkboxes and assuming user wants to post into the current group. Group administrators always see checkboxes." Brian
Will there always be a one-to-many relationship from user to portfolio piece? If so, just have them create "portfolio piece" nodes, then setup a view at user/$arg/portfolio. $arg is the userid. That will then show you all of user 5's portfolio nodes on user/5/portfolio, all of user 9's portfolio nodes on user/9/portfolio, etc. Cheers. --Larry Garfield On Wed, 17 Oct 2007 11:00:55 +0200, Daniel Carrera <daniel.carrera@zmsl.com> wrote:
Hello,
I need a way to make it easier for users to create an on-line portfolio of their work (the users are students doing school projects). The way we've been doing it so far is that they just make regular HTML pages. This means that the pupil must be mindful to keep an index page or else it'll be impossible to find their work scattered all over the site.
I would love to have something that kept a group of pages together. I looked at the "book" content type and I liked it, BUT anyone can insert a page in anyone else's book. That's not what we want. We also don't want each user to be faced with a list of 2,000 "books" to choose from when Drupal asks to which book they want to add their page.
Can anyone think of a better alternative?
I took a look at the E-Journal module and that didn't do what I wanted either. E-Journal is to create a regular publication with issues and volumes and the like.
Using a Blog would normally be a possibility, except that one of their projects that involves keeping a blog to record their progress.
Any ideas?
Thanks for the help.
Daniel. -- [ Drupal support list | http://lists.drupal.org/ ]
Larry Garfield wrote:
Will there always be a one-to-many relationship from user to portfolio piece?
Yes. - Each pupil will have multiple portfolio pages. - Each portfolio page will belong to exactly one pupil. If two students work on a project together they can each make a separate page about it.
If so, just have them create "portfolio piece" nodes, then setup a view at user/$arg/portfolio. $arg is the userid. That will then show you all of user 5's portfolio nodes on user/5/portfolio, all of user 9's portfolio nodes on user/9/portfolio, etc.
That sounds just perfect, but I don't know how to do it. How do the pupils create a "portfolio piece" node and how do I create a view for it? Can I create a new content type and call it "portfolio node"? If so, how? Thanks for the help! Daniel.
Hello, Daniel, Part of the challenge of designing a good portfolio app is that everybody thinks of different things when they think about a portfolio. The UI gets even more complicated if, for example, you want your students to be able to create a custom order for their artifacts -- You've gotten some good info in this thread so far, particularly with respect to views and the portfolio page content type -- some additional comments included inline below -- Daniel Carrera wrote:
Larry Garfield wrote:
Will there always be a one-to-many relationship from user to portfolio piece?
Yes.
- Each pupil will have multiple portfolio pages. - Each portfolio page will belong to exactly one pupil.
If two students work on a project together they can each make a separate page about it.
You might want to look at cck and nodereferences here -- using this functionality, your students could reference one piece of content from within another.
If so, just have them create "portfolio piece" nodes, then setup a view at user/$arg/portfolio. $arg is the userid. That will then show you all of user 5's portfolio nodes on user/5/portfolio, all of user 9's portfolio nodes on user/9/portfolio, etc.
This is created using the views module. However, I would recommend setting the $arg to username instead of userid, as the usernames tend to be more friendly than a number.
That sounds just perfect, but I don't know how to do it. How do the pupils create a "portfolio piece" node and how do I create a view for it? Can I create a new content type and call it "portfolio node"? If so, how?
Use CCK and Views. The Views Bonus Pack is also very helpful. http://drupal.org/project/cck http://drupal.org/project/views http://drupal.org/project/views_bonus Cheers, Bill -- Bill Fitzgerald http://www.funnymonkey.com Tools for Teachers 503.897.7160
Thanks! Great info. I didn't know about CCK. Cheers, Daniel. Bill Fitzgerald wrote:
Hello, Daniel,
Part of the challenge of designing a good portfolio app is that everybody thinks of different things when they think about a portfolio.
The UI gets even more complicated if, for example, you want your students to be able to create a custom order for their artifacts --
You've gotten some good info in this thread so far, particularly with respect to views and the portfolio page content type -- some additional comments included inline below --
Daniel Carrera wrote:
Larry Garfield wrote:
Will there always be a one-to-many relationship from user to portfolio piece?
Yes.
- Each pupil will have multiple portfolio pages. - Each portfolio page will belong to exactly one pupil.
If two students work on a project together they can each make a separate page about it.
You might want to look at cck and nodereferences here -- using this functionality, your students could reference one piece of content from within another.
If so, just have them create "portfolio piece" nodes, then setup a view at user/$arg/portfolio. $arg is the userid. That will then show you all of user 5's portfolio nodes on user/5/portfolio, all of user 9's portfolio nodes on user/9/portfolio, etc.
This is created using the views module. However, I would recommend setting the $arg to username instead of userid, as the usernames tend to be more friendly than a number.
That sounds just perfect, but I don't know how to do it. How do the pupils create a "portfolio piece" node and how do I create a view for it? Can I create a new content type and call it "portfolio node"? If so, how? Use CCK and Views. The Views Bonus Pack is also very helpful.
http://drupal.org/project/cck http://drupal.org/project/views http://drupal.org/project/views_bonus
Cheers,
Bill
Check also the bookexpand module. According to its description, you can restrict where users can add child pages, by user, by role, or by OG. http://drupal.org/project/bookexpand On 10/18/07, Daniel Carrera <daniel.carrera@zmsl.com> wrote:
Thanks! Great info. I didn't know about CCK.
Cheers, Daniel.
Bill Fitzgerald wrote:
Hello, Daniel,
Part of the challenge of designing a good portfolio app is that everybody thinks of different things when they think about a portfolio.
The UI gets even more complicated if, for example, you want your students to be able to create a custom order for their artifacts --
You've gotten some good info in this thread so far, particularly with respect to views and the portfolio page content type -- some additional comments included inline below --
Daniel Carrera wrote:
Larry Garfield wrote:
Will there always be a one-to-many relationship from user to portfolio piece?
Yes.
- Each pupil will have multiple portfolio pages. - Each portfolio page will belong to exactly one pupil.
If two students work on a project together they can each make a separate page about it.
You might want to look at cck and nodereferences here -- using this functionality, your students could reference one piece of content from within another.
If so, just have them create "portfolio piece" nodes, then setup a view at user/$arg/portfolio. $arg is the userid. That will then show you all of user 5's portfolio nodes on user/5/portfolio, all of user 9's portfolio nodes on user/9/portfolio, etc.
This is created using the views module. However, I would recommend setting the $arg to username instead of userid, as the usernames tend to be more friendly than a number.
That sounds just perfect, but I don't know how to do it. How do the pupils create a "portfolio piece" node and how do I create a view for it? Can I create a new content type and call it "portfolio node"? If so, how? Use CCK and Views. The Views Bonus Pack is also very helpful.
http://drupal.org/project/cck http://drupal.org/project/views http://drupal.org/project/views_bonus
Cheers,
Bill
-- [ Drupal support list | http://lists.drupal.org/ ]
participants (7)
-
Allen Stern -
bchoc＠t4tcolorado.org -
Bill Fitzgerald -
Cog Rusty -
Daniel Carrera -
Earnie Boyd -
Larry Garfield