uploads : Managing uploaded files¶
lino.modlib.uploads plugin adds functionality for managing "uploads".
It holds the minimal core functionality. There is also the
lino_xl.lib.uploads plugin, which extends this plugin and which is
described in Uploads with expiration date management.
This is a tested document. The following instructions are used for initialization:
>>> from lino import startup >>> startup('lino_book.projects.min9.settings') >>> from lino.api.doctest import *
- upload entry¶
A database record that represents an independent media file that has been uploaded to the Lino site either via the web interface or as a library file.
- upload file¶
A synonym for upload entry.
- uploads folder¶
The root folder below which all uploaded files are being stored on the server.
We differentiate between web uploads and library uploads. They look quite similar to the end user who may even ignore that difference. But they differ by the way they arrived to the server. Web uploads were uploaded manually by some user via the web interface, while library uploads have been discovered by Lino in a library volume. Web uploads are stored below the uploads folder while library uploads are stored below the folder given by their library volume.
A third type of upload files are fileless uploads. Yes, you can even have upload files without an actual file. This represents the fact that some external document exists, but just hasn't been digitalized. There are people are interested in this kind of fact ;-)
Every upload file is usually linked to its controller, i.e. some database object that inherits from
UploadController. Upload files without a controller are considered
useless, and the site manager should decide what to do with them.
- library volume¶
A folder in the file system where library uploads are stored.
Django model representing an upload file.
The size of the file in bytes. Not yet implemented.
The media type of the uploaded file.
See also this thread about length of MIME type field.
The type of this upload.
UploadType. The choices for this field are usually limited to those in the same upload area.
A short description entered manually by the user.
The path of this file, relative the volume's root.
Mixin for tables of uploads where the area is known. Inherited by
The summary displays the uploads related to this controller as a list grouped by uploads type.
Note that this also works on
lino_welfare.modlib.uploads.models.UploadsByProjectand their subclasses for the different _upload_area.
Shows my uploads (i.e. those whose author is the current user).
Shows the uploads controlled by this database object.
Abstract base class of
Upload. This was named
lino.mixins.uploadable.Uploadableuntil 20210217. It encapsulates some really basic functionality. Its usage is deprecated. If you were inheriting from
lino.mixins.Uploadable, you should convert that model to point to an
The application developer can define upload areas. Every upload area has its list of upload types. The default has only one upload area.
>>> rt.show(uploads.UploadAreas) ======= ========= ========= value name text ------- --------- --------- 90 general Uploads ======= ========= =========
For example Lino Welfare extends this list.
Django model representing an upload type.
The table with all existing upload types.
This usually is accessible via the Configure menu.
The application developer can define upload shortcuts. Every upload shortcut will create an upload shortcut field, a virtual field with a set of actions for quickly uploading or viewing uploads of a particular type for a given database object.
Declare your Site's upload shortcuts from within your
workflows_module. For example:
from lino.modlib.uploads.choicelists import add_shortcut as add add('contacts.Person', 'uploaded_foos', _("Foos"))
uploaded_foosfield visible in some detail layout.
Using the web interface, select, create an upload type named "Foo" and set its shortcut field to "Foos".
Upload a file from your PC to the server.
Open the uploaded file in a new browser window
The list of available upload shortcut fields in this application.
>>> rt.show(uploads.Shortcuts) No data to display
Declare an upload shortcut field. This is designed to be called from within your