Yes, we've been discussing ideas to implement these. The problem with 
metadata as it is right now is that internally it is a dumb text field. If 
two separate values are added internally it will still be just one field 
with two values concatenated and separated by a delimiter (a comma, 
semicolon, etc). The problem is that if one value use the same character as 
the delimiter the field doesn't know where one values ends and the next one 
begins. This is a a typical problem with structures in databases and the 
approach I just explained is what Django itself uses for its mutli values 
field, but doesn't work for all cases. One problem with multiple values is 
that search feature breaks. The search code would be to interpret the 
multiple values of each metadata for each document. 

We have talked about adding support for metadata widgets that will filter, 
validate and serialize the data from the user for storage and the 
deserialze the data to display it in its original form. Widget will allow 
setting a metadata value's type: Date, number, string, multi string, 
choices. Internally they are all strings but at the UI level different data 
types are emulated. Widgets solve the problem of data validation, data type 
validation, dependent values,and multi values. Sadly they break search too 
as explained above. This feature can't be added until the issue with the 
search is solved.

On Tuesday, March 6, 2018 at 4:16:33 PM UTC-4, Mark Phillips wrote:
>
> Any thoughts on making metadata select boxes have (1) the ability to 
> select more than one option per metadata, and (2) chained metadata 
> selections - ie one selection determines the values for the second 
> selection?
>
> Thanks!
>
> Mark
>
> On Tue, Mar 6, 2018 at 3:31 AM, <[email protected] <javascript:>> wrote:
>
>> We are keeping the project alive and released a new version based on 
>> direct input and guidance from Roberto. It was released as Mayan EDMS NG 
>> 2.8. NG as in Next Generation. It is a 100% compatible fork. We are working 
>> right now on version 3.0.
>>
>> On Thursday, November 30, 2017 at 10:44:16 AM UTC-4, Mark Phillips wrote:
>>>
>>> Mayan lives in Puerto Rico, and Maria happened. Mayan is still alive and 
>>> well, just digging out from under the rubble.
>>>
>>> Mark
>>>
>>> On Thu, Nov 30, 2017 at 12:26 AM, Tony Nys <[email protected]> wrote:
>>>
>>>> Hello All
>>>>
>>>> Mayan seems to be hibernating for a long winter sleep.
>>>> Previously, there was a new release every 2 to 3 weeks.
>>>>
>>>> * The latest, 2.7.3 release is 3 months old, released September 11 2017
>>>> * Little or no activity of the main developer on the forum: Roberto 
>>>> Rosario
>>>> * Last code commit on September 11
>>>> * no reaction on bugs 
>>>>
>>>> -- 
>>>>
>>>> --- 
>>>> 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/d/optout.
>>>>
>>>
>>> -- 
>>
>> --- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 

--- 
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/d/optout.

Reply via email to