I was looking at Django 
Selectable: https://bitbucket.org/mlavin/django-selectable, which uses 
jqueryui to build comboboxes and other auto-complete type fields.  Pretty 
nice.  But I haven't quite dug in deep enough to get this whole concept 
working.  I've never written python, and I obviously haven't messed with 
Django.  There's a rather steep learning curve.  If I knew what I was 
doing, it would probably be a 4-5 hour project.  Not knowing what I'm 
doing, it could take 30-40.  I'm still looking at other options for my 
document management, including SharePoint, which our IT staff uses a lot. 
 I'd prefer to use a standalone Linux system for this particular project, 
but right now I just need a solution quickly.

I totally agree on the typing -- having integers, dates, etc. would be very 
helpful.  

Also I'd love to see support for required vs optional metadata (I see that 
Roberto has some support for this in his code; it's just not working yet).

As long as I'm being wishful, I could imagine a full business rule system; 
maybe you would code the rules in python or something...

On Tuesday, April 9, 2013 1:59:59 PM UTC-4, Mike Hadmack wrote:
>
> Jason,
>
> I'm glad I'm not alone in this.  Without this feature there will be too 
> much fragmentation in the database to do any useful indexing.  If you do 
> any development work on this can you share your fork?  I'd be happy to help 
> out with it.
>
> It would be nice to have an editable combobox with completion while typing 
> but I think the only way to do this is with jQuery or a similar library. 
>  In my deployment it will be important to have a complete list of options 
> presented to the user.  I was also thinking of something like a "+" sign 
> next to a static combobox to add a new item via a popup.  I'm not sure if 
> HTML combo box option lists are mutable through JS though?
>
> Another thing that is troublesome with metadata is the lack of datatypes. 
>  I need to add a date field but it would be nice to have formatting 
> validation and maybe a picker available, otherwise there will be no way to 
> sort documents by data.
>
> -Mike
>
>
>
> On Tue, Apr 9, 2013 at 7:30 AM, Jason Priebe <[email protected]<javascript:>
> > wrote:
>
>> Mike:
>>
>> This is an important feature for us, too.  It's pretty much a 
>> deal-breaker.  We can't have users all entering names inconsistently.  At 
>> least having a dropdown of suggested values would help bring some 
>> uniformity to the process.
>>
>> I'm envisioning things working like this:
>>  - when defining the MetadataType, there is a boolean that indicates 
>> "enforce lookup"
>>  - if enforce_lookup is true, the form presents an HTML select field
>>  - if enforce_lookup is false, the form presents a text field, and it 
>> uses javascript to retrieve the lookup values as the user types  (you could 
>> use your technique of a select field and a text field, but that would be a 
>> little cumbersome for the user)
>>
>> Then you could enter the python database code in the lookup field when 
>> you define the MetadataType.
>>
>> I'm very close to trying to tackle this myself.  I really like Mayan in 
>> comparison to other products, but we really must have this feature (along 
>> with a couple of others).
>>
>>
>> On Friday, April 5, 2013 9:05:24 PM UTC-4, Mike Hadmack wrote:
>>>
>>> Hi Lau,
>>>
>>> I don't know that any JS would be required for this feature.  I don't 
>>> think it would be difficult for the Mayan backend to query the database for 
>>> a list of all metadata values and fill in a combo box.  In the case of a 
>>> static set of metadata values this could be done by a function called from 
>>> the "Lookup" property of the metadata type.  I think that the only 
>>> complication is the addition of a text field beside the combo box that 
>>> would allow for entry of new values.  This doesn't sound particularly 
>>> complex but will require someone with much more Django knowledge than I.
>>>
>>> -Mike
>>>
>>> On Friday, April 5, 2013 5:21:43 AM UTC-10, Lau Llobet wrote:
>>>>
>>>>  Hi Mike, I find this feature usefull. Although web browsers tend to 
>>>> place already used values to the textboxes while writing. 
>>>>
>>>> This solution solves the problems derived from having large lists of 
>>>> metadata, together with the solution proposed on the "metadata fixed 
>>>> values 
>>>> subsets to avoid long lists" e-mail It would make the metadata description 
>>>> more easy.
>>>>
>>>> Both solutions require Java Script in the same web page in order to 
>>>> display this features. We could consider contacting a developer in order 
>>>> to 
>>>> do this client side coding (JS) while Mayan developers should do the 
>>>> server 
>>>> side. They also shoud check if the Puerto Rico laws about accesibility 
>>>> allow this features for disabled people usage. Maybe there's a flag on the 
>>>> web browser of the disabled person that can trigger the classic web view 
>>>> that's currently implemented.
>>>>
>>>> Hope to hear from you,
>>>>
>>>> Lau
>>>>
>>>>
>>>> On Sun, Mar 31, 2013 at 10:15 AM, Mike Hadmack <[email protected]>wrote:
>>>>
>>>>> Hi Everyone,
>>>>>
>>>>> Is there a way to allow a metadata field accept the entry of a new 
>>>>> string value AND present the user with a list of existing values from the 
>>>>> database.  Since the metadata Lookup can execute python code it should be 
>>>>> possible to generate a list of existing values as choices, but then I 
>>>>> need 
>>>>> to allow the user to add new choices to the list.  I am pretty new to 
>>>>> Django so I don't know how much work would be involved in implementing 
>>>>> this 
>>>>> feature.  Can this all be accomplished by modifying DocumentCreateWizard?
>>>>>
>>>>> Thanks,
>>>>> Mike
>>>>>
>>>>>  -- 
>>>>>  
>>>>> --- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "Mayan EDMS" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to mayan-edms+...@googlegroups.**com.
>>>>> For more options, visit 
>>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>>> .
>>>>>  
>>>>>  
>>>>>
>>>>
>>>>  -- 
>>  
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Mayan EDMS" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/mayan-edms/NuwHTS7LiYM/unsubscribe?hl=en-US
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to