This should be very easy to do in BoltWire. A few suggestions:
1) I'd suggest a name beside whiteboard as it has another meaning to
most people. What about jobboard or jobs or something
2) Though there are several ways to index information to generate
reports (spec: data and info vars) the fastest and easiest is actually
in the page name. Data vars can be slow (as each page has to be opened
and read) and info vars keep the info separate from the page (so there
is always the syncing issue). So I'd suggest a page name scenario like
the following:
jobs.open.dept1.timestamp
jobs.closed.dept2.timestamp
3) The allows you to restrict your searches very quickly:
[(search group=jobs.open*)] all open
[(search group=jobs.open.dept1*)] all open in dept1
[(search group=jobs if="equal {+p3} dept1")] all in dept1, closed or open
4) Sorting is done by
[(search group=jobs.open* sort=lastmodified)] Last edited.
[(search group=jobs.open* sort=p4)] Submission date
If the order is backwards for either, try order=reverse.
5) Create a little form that generates your search parameters
something like this (other ways to do it of course):
[form]
[select status default='{:status}'][option open][option closed][select] `
[select dept default='{:dept}'][option '*' all][option .dept1*
dept1][option .dept2* dept2][option .dept3* dept3][select] `
[select sort default='{:sort}'][option 'lastmodified' modified][option
'p4 order=reverse' submission][select] `
[submit GET]
[session passdata dept]
[session savedata status,dept,sort]
[form]
[if set "{?dept}"]
<(search group=jobs.{:status}{:dept} sort={:sort})>
[else]
<(search group=jobs.open* sort=lastmodified)>
[if]
You still need to create the form to generate the pages, and edit
them, but this should take care of the searching and sorting and the
like...
Cheers,
Dan
On Sun, Sep 20, 2009 at 7:24 AM, Kevin <[email protected]> wrote:
> One of the reasons why I was looking at time for page creation is because on
> Friday night, I realized that Boltwire most likely could do something
> internally that I planned on adding to the HelpDesk app we use. I planned
> on coding it next week in the HelpDesk but thought I'd give it a shot in
> boltwire first.
>
> It is what I call a Whiteboard. Basically, it is a central place for issues
> to be posted so that the IT staff can easily find and see them. We have
> many issues that arise from time to time which end up generating tons of
> duplicate tickets, calls and emails which would be easily remedied if the
> issue was broadcast in a central location when identified.
>
> So... What I planned on doing was creating a Whiteboard system in boltwire.
> I thought it could work like this...
>
> The system would use whiteboard as the file name base. Each new issue would
> be dated to keep them in order (with a unix timestamp now) so that
> whiteboard.1253444780 would be the same as 2009-09-20 04:06:20...
>
> On the main whiteboard page, i would have a search function that would list
> the pages in newest to last order that would display in a table info
> collected including the Status (from a data field on each page), Creation
> date from the filename and Title. Title would be a link to the page so that
> details could be viewed.
>
> Also on the page would be a form that would create new whiteboard pages.
>
> The form would ask for the Title, perhaps main contact name and a
> description and ETA and other stuff, but start out very basic, and on save
> would create the page, set the title = title description, save the status as
> data in the page to Open...
>
> When viewing a page, there would be a form that would allow updating the
> issue with more detail, by adding to the existing page using a similar form
> as the creation. One option would be to change the status of the page from
> Open to Closed or Canceled which would update the data variable status.
>
> While the pages themselves could be edited using normal edit, the idea of
> using forms for adding to them and editing them is most likely more useful
> as then anyone could use it to add new and update existing whiteboards. The
> easier the better as then it would actually have a better chance of being
> used (people don't use things they can't figure out).
>
> For the concept as a whole, I pretty much have and Idea how to do most of
> this... but was having issues getting details on parts of it with the
> boltwire site having issues.
>
> Not sure if anyone else would want/need something like this, but I can think
> of a couple sites I would immediately use this on.
>
> Now that it appears the issues on the boltwire site is corrected, I will
> look at it again in the morning (real morning, not now) as I put it off to
> later because I was running into dead ends.
>
> Specifics I was looking for.
>
> o Was file creation but I've got that now.
> o Search routine that would find the pages (in most recent first), extract
> the data from the status data varaible and display the status, date of page,
> and title
> o How to make the form save the title for the page from the title
> description entered. Think I've got that now too.
> o dealing with the update stuff. Haven't thought that out yet except in
> concept.
>
> There might be an existing plugin that does something like this now. Wasn't
> sure if using sub-pages would be easier for updates to the white board with
> just updating the data value in the main file with whiteboard status. don't
> really think any PHP would be needed except perhaps the table stuff as I
> really haven't figured out the search stuff well yet.
>
> Just thought I'd throw the idea out there...
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
