I've got some Java code (GIT repo at
https://github.com/shorero/ExifExtractor.git) that looks for images in
Mayan, extracts EXIF metadata, and adds the EXIF information to Mayan as
metadata tags. This could probably be modified to do what you need.
On Thu, Apr 19, 2018 at 4:14 PM, Pablo Castro
I don't know either Django or Python, and the documentation is a bit skimpy
on examples for templates used to structure metadata. How about some
examples? Common problems I have are:
* Timestamping a document with "date created", rather than simply the date
updated, with enforced format
hu, Feb 22, 2018 at 5:51 AM, RW Shore <rws@shore.support> wrote:
>
>> I don't know either Django or Python, and the documentation is a bit
>> skimpy on examples for templates used to structure metadata. How about some
>> examples? Common problems I have are:
>>
>>
Does anyone have a transformer that maps the embedded JPEG metadata
(date/time taken, size, ...) into Mayan-EDMS metadata? Is such a
transformation possible?
--
---
You received this message because you are subscribed to the Google Groups
"Mayan EDMS" group.
To unsubscribe from this group and
Ignore the last posting. I had the authentication configured incorrectly.
It's rolling now.
--
---
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
I'm trying to write a client that hits the Mayan-EDMS REST API. I'm not
getting any errors, but I'm not getting any meaningful information back.
For example, I've got two tags defined, and when I hit api/tags/tags from
my browser, I get the expected JSON structure back. However, when I hit it
from
re version 2.8: do you plan to have a Docker container as well? (hint hint
:-)
On Tue, Feb 27, 2018 at 5:40 AM, wrote:
> Hi all,
>
> We love Mayan EDMS and have come to depend on it for our daily work. Like
> many of you we are worried about the effects hurricane Maria
hael Price 2018-03-10
>> 13:18:55 -0400 170)
>>
>>
>> On Tuesday, March 13, 2018 at 1:24:31 AM UTC-4, ericr...@gmail.com wrote:
>>>
>>> I think metadata types are already sorted. I'll take a look.
>>>
>>> On Saturday, March 10, 2018 at 6
Let me know if I've messed up anything
On Tue, Mar 13, 2018 at 1:23 AM, <ericrigg...@gmail.com> wrote:
> Sweet! I gonna give it a try.
>
>
> On Saturday, March 10, 2018 at 11:27:42 AM UTC-4, RW Shore wrote:
>>
>> I have created an external, Java application that add
uthenticated.
>
>
> On Tuesday, March 13, 2018 at 1:32:15 AM UTC-4, ericr...@gmail.com wrote:
>>
>> Request a token from /api/auth/token/obtain/ and include it in your
>> request headers.
>>
>> On Wednesday, March 7, 2018 at 3:31:39 PM UTC-4, RW Shore wrote:
>&g
The documentation for the API function that creates a new tag (POST
/api/tags/tags) indicates an optional parameter documents_pk_list. This
parameter does not actually exist; a POST request to this function that
includes field documents_pk_list fails with a 400 (Bad Request) response.
--
---
I have created an external, Java application that adds EXIF metadata as
metadata fields to Mayan-maintained images. The app is on GitHub at
https://github.com/shorero/ExifExtractor.git
Feel free to use, to ask me questions, or to suggest changes.
--
---
You received this message because you
I've successfully written a Java program that adds EXIF values as metadata
to images stored in Mayan. The program also adds any metadata fields that
don't exist, processes only images with a special 'unprocessed' tag which
it removes, pays attention to allowed metadata fields for a document type,
The ordering of metadata tags is not consistent from page to page. In
particular, the display on the document-type setup page where one specifies
the allowed metadata types for a document type sorts the metadata types
alphabetically by label. The display of metadata fields on the
recent-documents
epository:
>
> https://gitlab.com/startmat/document_analyzer
>
> br
> Matthias
>
>
> Am Freitag, 2. März 2018 18:01:19 UTC+1 schrieb RW Shore:
>
>> thank you for the suggestion. Unfortunately I can't get the
>> document_analyzer app to install. My situation is the
Actually, the whole volume stuff should be taken as a low-priority
suggestion. I've got my service build working now, and was even able to add
a new analyzer function (from GIT repo
https://gitlab.com/startmat/document_analyzer.git) to an extension of the
docker image. I'd rather see a focus on
I have a small docker swarm of 4 NUC-sized machines (mix of Core i5 and
Core i7 CPUs) plus one old laptop (Core i5); each of the 5 hosts runs
Fedora. Mayan and its database are running as two services in the swarm,
attached to a mayan-specific docker network. The docker volume runs under a
rsday, March 15, 2018 at 1:31:44 PM UTC-4, RW Shore wrote:
>>
>> The documentation for the API function that creates a new tag (POST
>> /api/tags/tags) indicates an optional parameter documents_pk_list. This
>> parameter does not actually exist; a POST request to this func
the only thing I actually did was "exiftool -ver".
Any suggestions?
On Fri, Mar 2, 2018 at 6:10 AM, Matthias Löblich <mloebl...@gmail.com>
wrote:
> You can also use https://gitlab.com/mayan-edms/document_analyzer, which
> includes the exif functionality.
>
> b
Never mind my previous posting. I missed the "tags" menu selection on the
GUI.
--
---
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
20 matches
Mail list logo