Showing posts with label Employment. Show all posts
Showing posts with label Employment. Show all posts

Tuesday, April 02, 2013

Looking for a consultant on a "Drupal6-based collaborative workspace"

Sharing this email to see if someone knows of a consultant who can assist on this project.
Hello Friends, 
I'm using LinkedIn to find quality consultants to bid on a project my organization is spec'ing out. I have not contacted many of you in many years, so please don't be offended if you feel this is kind of spammy, but I thought you might know someone interested in responding to this RFI we have crafted: 
http://library.cee1.org/content/emerging-technology-assessment-catalog-tool-request-information 
I'm facilitating the project for a colleague--I have my hands full. The RFI is a tool we are using instead of an RFP or just diving in and adding this project to my workload with my one existing contract developer. 
So far, the kinds of responses I'm getting are basically: "I'm a smart developer and charge @25/hr; when can we start?" We need someone who will actually read the RFI and respond. 
If you would like to pass this on to trusted people you know--or have feedback for me--I would appreciate that very much!

Thank you!
--Dave Atkins

Here's a more specific and technical commentary from me that frames the project:

The attached Request for Information (RFI) describes our need for a tool that will allow collaborative management of information similar to a shared spreadsheet and be compatible with our Drupal6-based collaborative workspace. We are open to different approaches--whatever works most efficiently with our project--but my preference is to integrate this solution in a way that it can be used for other situations where we need to gather and manage data from multiple organizations who use our workspace.

Our workspace/extranet is a highly-customized Drupal site organized around organic groups with complex permissions. One approach could be to create a new custom content type and then assign the nodes created with this type to the appropriate organic group, so the resulting "document" would only be accessible to other group members. An alternative approach would be to develop a custom php-based application with its own database, then integrate authentication. A third path would be the completely non-integrated solution or some off-the-shelf product that automagically does it all. Because we don't have enough information to choose an architectural path, we developed this RFI. However, you may choose whatever approach you feel most expert in and propose a solution. If we receive multiple similar solutions we will followup with questions to identify the best proposal.

Some things to consider:

  • The solution needs to be easy for the end users. They have their own systems containing the data to be uploaded and will not be asked to change or conform their datasets to a standard. We need to give them a one-time data mapping wizard that works for both import and update.
  • We do not want to design data entry screens. Users are not going to be asked to copy and paste from the screens of their systems to another system.
  • We do expect non-technical end users will perform the initial data mapping or follow a simple procedure such as export to XML, then import with this tool. We need this general approach to avoid having to write custom ETL scripts for every user. We do not have that level of access to the users: we need to give them a finished working tool, not more work.


The budget for this project is somewhat flexible. We don't expect credible solutions for $500, but we also do not view this as enterprise software development. It should be doable in the 1-2 month timeframe following an agile approach where, once engaged, you work with us to test and refine the solution.

Tuesday, November 25, 2008

Job searching notes - contract or assignment #

One of series of tips from a local networking group of folks who are or have been at one time looking for new work. These are considerations; one might provide a disclaimer that the mileage on these suggestions may vary. Through the sharing and collaboration, these may at least spark some useful thought process that will ultimately lead you to a successful position.

If you are working with a recruiter, obtain the contract or assignment number for the posting that you are working with him/her on. It may be that if you are working with multiple recruiters, that you could be replying for the same position from two recruiters. Not good. Having the number will help you keep track of which position or opportunity you are working on with each recruiter.



Reblog this post [with Zemanta]