Hi,
Sadly there is nothing right now to automatically set a metadata value
after the document is uploaded or renamed. A custom app would need to be
created for this that would allow to define a macro or script.
On Friday, January 8, 2016 at 5:04:46 PM UTC-4, Rachael Sewell wrote:
>
> Hi Roberto,
>
> This works great. An additional requirement that I will need is to
> automatically equate the DocNum metadata field to the document number
> generated from the new document_renaming app. Is there a way to provide a
> metadata field that is auto-populated?
>
> Rachael
>
> On Thursday, December 24, 2015 at 12:18:43 AM UTC-8, Roberto Rosario wrote:
>>
>> HI, I did a small lab and these are the steps (screen shots attached):
>>
>> - Create metadata types DocNum and CrossRef.
>> - Create the document types: Spec and Memo
>> - Add the metadata types (DocNum and CrossRef) to both document type (I
>> added them as optional metadata for the demo, DocNum could be required in
>> production).
>> - Create smart link as shown, add Dynamic Label: {{
>> document.metadata_value_of.CrossRef }} to display an easier to read title.
>> If a static title is desired use a quoted string instead,
>> - Add the smart link to the document types.
>> - Create 2 conditions for the smart link, one to match the value of the
>> source document's CrossRef metadata value to all other documents' metadata
>> values. And another to match only the foreign documents' DocNum metadata
>> type.
>>
>> Smart link results for each document will be available on the 'Smart
>> Links' tab of the document. Some further tuning might be needed depending
>> on your requirements such as assigning DocNum to Spec only and CrossRef to
>> Memo, and assigning the smart link only to Memo doc type if you only need
>> to reference Specs in Memos and not Memos in Specs.
>>
>> On Friday, December 18, 2015 at 3:08:40 PM UTC-4, Rachael Sewell wrote:
>>>
>>> Hi Roberto,
>>>
>>> Thanks for your answers. I'm having trouble configuring the smart links.
>>> Here is what I want to do.
>>>
>>> Document type: Spec
>>> MetaData Internal Name: DocNum; Value: <String>
>>> MetaData Internal Name: CrossRef; Value: <DocNum>
>>>
>>> Document type: Memo
>>> MetaData Internal Name: DocNum; Value: <String>
>>> MetaData Internal Name: CrossRef; Value: <DocNum>
>>>
>>> I want to create a smart link that will link a document of any type when
>>> the CrossRef value matches the DocNum.
>>>
>>> Rachael
>>>
>>> On Wednesday, December 16, 2015 at 2:41:56 PM UTC-8, Roberto Rosario
>>> wrote:
>>>>
>>>> Hi, thanks for considering Mayan EDMS for your project.
>>>>
>>>> It is not possible to add attachments for document versions at the
>>>> moment. The closest feature already in place is smart links which allow
>>>> linking or referencing documents, but it is a document-centric link and
>>>> not
>>>> per version. Smart links work by creating rules based document properties
>>>> or metadata. There is no provision for manual creation of document links.
>>>>
>>>> Documents are not converted, they are stored in the document store
>>>> exactly as uploaded, only their filename is replace by an UUID to avoid
>>>> filename collisions. This is to avoid vendor lockin and preserve document
>>>> integrity (in documents used as evidence for legal cases for example).
>>>> Only
>>>> the document's visual representation is modified.
>>>>
>>>> There is a ticket to add subscription and notification for documents,
>>>> but it is still in an early stage. There is no roadmap yet for version 3.0
>>>> and this could be one of the features pushed for inclusion.
>>>>
>>>> At one time there was an example in the FAQ how to integrate with LDAP,
>>>> it was remove as it became obsolete. Mayan uses Django (a Python web
>>>> framework) so any example on how to integrate Django with LDAP should work
>>>> with Mayan.
>>>>
>>>> Development work is always needed and appreciated, pull request and
>>>> tickets are welcomed for these or any other features, if they are not
>>>> integrated into the core implementation they can be developed as custom
>>>> app. Two examples started just a few days ago:
>>>> https://gitlab.com/mayan-edms/versionlifespan and
>>>> https://gitlab.com/mayan-edms/exif
>>>>
>>>> UI enhancements are much needed and now that we changed to a Bootstrap
>>>> based UI should be easier to implement, feel free to open another thread
>>>> to
>>>> discuss those.
>>>>
>>>> Thanks,
>>>>
>>>> --Roberto
>>>>
>>>> On Tuesday, December 15, 2015 at 2:36:02 PM UTC-4, Rachael Sewell wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I am evaluating SeedDMS, OpenDocMan, and Mayan-EDMS for an internal
>>>>> company document management system. Many of the features that we need for
>>>>> our basic requirements are included already. However, I'd like your
>>>>> opinion
>>>>> or roadmap for some additional features.
>>>>>
>>>>> Our documents can contain any number of attachment documents. These
>>>>> attachments are per version. Also, we convert all docs to pdf including
>>>>> attachments. Is there any functionality in Mayan currently that would
>>>>> allow
>>>>> adding attachments? Are documents converted and stored as a pdf?
>>>>>
>>>>> The smartlinks appear to be close to what we need. We have several
>>>>> documents that point to other documents. We need to maintain these
>>>>> cross-references and citations. Does the smartlinks feature allow that?
>>>>>
>>>>> Is there any plan to add a bookmarking/subscription feature to
>>>>> documents on a per-user basis?
>>>>>
>>>>> We can only perform LDAP authentication. Is there any plan to add this
>>>>> feature in the future.
>>>>>
>>>>> Finally, if any of these features are not currently planned would it
>>>>> be possible to become a contributor and work on these features? I also
>>>>> have
>>>>> some User Interface ideas to get tasks done with fewer clicks.
>>>>>
>>>>> Thanks in advance,
>>>>> Rachael
>>>>>
>>>>
--
---
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
