use cases

Scenario:

To get started, I have an organization that needs some very basic CRM added to its Drupal (6) site. The org has been using a Facebook group as its CRM, which works for maintaining a simple membership roster, group emailing, posting notices, and handling invitations/RSVPs for events. Events data is synched from Facebook to Drupal, via a bookmarklet I wrote. The org's membership is between 150 and 200 and administration is all volunteer.

Here are some use cases that I've received from my mentors. There are some great ideas here, and I hope to implement as many as I can. Please add you ideas if you have any.

Events Integration
If you have events posted on your website, you should be able to collect cell phone numbers in your event sign up form and then use them to send an SMS blast if there is a last minute change in location, a weather update, or even a full parking lot.

• Show field for mobile number on RSVP form
• Enable on an event-by-event basis

CCK Integration

It's a question that I wanted to ask long before. Kreynen's story of how the University of Nevada could use an aggregator for covering the Tahoe fire makes me finally post: What are you using an aggregator for?

Do you think that what we have at ?q=admin/user/access is enough to reflect uses cases of a system ?

I found it very powerful and you ?

What do you need from a Drupal PDF module? Do you need it to format a web page just to send it to the printer, or do you need it to generate a document like an invoice, a book, or catalogue?

How much theming and customization flexibility do you need?

I am a web architect and a system analyst. Now, I've translated Drupal To Hebrew and initiated the creation of a drupal community in Israel. Following Gábor Hojtsy's request, Here is a use-case analysis of my expernece from the Hebrew Translation of Drupal, and with it's implementation on tens of sites, with indexation for search engine relevancy.

Recently, I've tried the Internationalization module on two of my sites, but gave it up and decided to wait for a later time. Problem is that i18n is not yet compatible with many other modules. I am a heavy user of taxonomy / category modules. The i18n module is a big step forward, but more work is needed. I need language specific taxonomy with menu integration. On one site, I have tried to use the taxonomy module, but found that the vocabulary names are not translated (nither in the node entery screens nor in the menu). On the other site, I tried to use the new category module but discovered that the node input form (and the menu) displayed all categories without language distinction.

You have set up a website where multilanguage content submission and display was a requirement? What was the workflow specified by the customer? How were relations between different languages defined? Did you have all content translated? Was translation into specific languages a requirement for publication? Did you translate all navigation and even site level images? What was special about that project?

An internationalization use case consists of the requirements you faced, the user workflow you needed to support, and the interface you provided to the user. We are not interested in dirty implementation details (modules, PHP code, CSS) at this stage, only higher level information about how you built up multilingual content, interface, navigation and site design. You don't even need to talk about Drupal projects. If you have any other use cases to share, which you experienced out of Drupal, we are interested. The goal of the above questions are only to start you up, don't let them stop you from sharing your story in greater detail.

You can either post a new story to this group or comment on this story with your use case. Thanks for sharing!

Sorry, I would've posted this to the What do you want in a file API? thread, but unfortunately you can't attach files to comments.

These are some use cases that Shane Peery, one of our clients, wrote up for AMBuzz, an intranet site for a large media distribution company. They have some fairly complex needs, so I figured I'd post them here in the hopes they might inspire some of the folks working on this stuff, and also in case anyone had any bright implementation ideas. :)

I've also attached some general observations/comments he made regarding Drupal's file API as someone with experience in programming, but new to Drupal. Some of the stuff he mentions is relatively easy to sort out (for example, the security stuff is a matter of turning on private downloads and moving the files directory outside of public_html), but I think there are some interesting ideas here anyway.

Here is a draft of my latest pass at an Events 2.0 document. Published for the presentation at DrupalCon '06.

I've done more work to define what I think a reasonable "first pass" could look like for events. My objective is to establish end-to-end functionality, but to cut back on features so that this phase could be completed in a relatively short timeline. I have used the UCs from my original pass through and so this new diagram is a subset of the original: