Releases: onset/lameta
3.0.14-alpha
Various wording and tooltip customizations for ELAR.
3.0.15-alpha
Project metadata now separates project name and title more clearly, with updated behavior for displaying and migrating existing projects.
V3 field names were revised to simplify project language and description handling.
In ELAR mode, forms now show field tips more consistently, making archive-specific guidance easier to find.
Primary Occupation is once again included in IMDI export.
ELAR access wording has been updated to match current labels.
Compatibility and export updates
Added migration and compatibility handling for older project data so existing projects continue to work with the revised V3 field model
3.0.13-alpha
- Fix IMDI export using ISO6393-3 instead of ISO693-1
- For ELAR, remove North-America, Middle-America and South-America from the continent list. Americas only.
3.0.12-alpha
- Translatable Access description in consent documents
- Set IMDI type of "srt" files to "subtitles"
- Include translations for "actor" role in project document pseudo sessions
- Export "Other" gender to IMDI
3.0.11-alpha
Fixes
- Fixed a problem with getting the insertion cursor into an empty Notes tab
Improvements
- Enable translation of stock title and description strings used in IMDI export of project documents and consent documents.
- Add collection description as a translatable genre.
- For project documents create an element using the collection steward's name and the "research" role. Make that role translatable.
- Make the string "consent documents" translatable. This is used for description on the access of consent documents).
- Made it easier to preview what IMDI is going to be for consent documents and project documents:
3.0.10-alpha
Fixes
- Fixed contribution comments editing
- Fixed multilingual project title and description in IMDI exports
Improvements
- Made access description on project document multilingual for ELAR
- Made IMDI-introduced genres translatable
- Updated IMDI schema
Testing/Developer
- Added contributor comments tests
- Improved e2e test performance with fast launch bypass for intro screens
- currently at 1064 logic tests, 119 UI tests
3.0.9-alpha
Fixes:
- Fixed IMDI export of language ids and names
- IMDI export now only uses 3 letter codes
- Fixed adding previously unknown languages
- Made it easier to notice the "Change" button in the Archive chooser.
- Fixed display of languages to list the name; it was sometimes showing the code instead.
- Previously if you selected a language and then removed it, you could not choose it again until after reload
- Fixed IMDI output of Access description when multilingual
Improved:
- Searching in IMDI/Rocrate views
2.3.18
- Update AILLA protocols
- Update UI translations from Crowdin
- Another go at making the date picker ignore the user's time zone
3.0.8-alpha
Multilingual fields
Archives can now specify which fields to make multilingual, and which IMDI schema to validate against (ELAR now uses a draft IMDI 3.0 schema that supports the multilingual fields).
Multilingual Free-form fields
Multilingual “slots” for free-form fields are now fully functional:
Placeholders show you where to type:
If lameta doesn't know the language of some text, it will show like this
Multilingual Closed Vocabulary fields
Hover over a field to see all the translations that will be exported:
If a translation is missing for a value, the field shows a warning icon, and the tooltip gives you a link to where to fix it:
Project:Languages:Metadata Languages
We have introduced a field called Metadata Languages that does two things:
- Controls the order in which lameta shows each language slot:
- Some projects will be migrating from "slash notation". For these projects, until we finish the migration (see below), we need to know the order of these languages. This field does that for us.
Metadata Languages are numbered and re-orderable:
The order is used for two things:
Migration
A number of projects using lameta 2.x are already writing multiple languages in lameta fields. They are doing this by separating different slots with spaces and slashes, e.g.
This release includes a number of features designed to help you to safely migrate this data to a form in which lameta knows exactly what language each bit of text is in. This migration requires that every fields includes the same slots, in the same order. In order to help you verify that the conversion will work correctly, lameta postpones the actual migration until after the user has had a chance to look over all the fields.
When lameta detects taht a multilingual migration is pending, upon opening the project it will always take you to the Project:Languages screen. There, lameta will show a new "Migration Panel":
There must be at least two Metadata Languages defined before migration is possible. Until then you will see:
If lameta can tell that you may have left out a metadata language, it will warn you:
Once migration is successful, you will see:
lameta prevents IMDI export until you finalize the migration.
Language labels are mandatory until migration is complete, then optional:
For genres and roles, you can add translations here:
Other UI improvements
-
Added limited spell checking ability (English, Indonesian, French, German, Portuguese, & Spanish).
-
Added standard Cut/Copy/Paste (and related) context menu items.
Performance
- Large projects now load 12x faster.
Fixes
- Fixed a problem with OPEX schema validation.
- Fixed an issue that could import folders with detected problems during CSV import.
- Fixed a possible problem when adding contributions if some contributions did not have People entries yet.
- Fixed a possible problem if two people's IDs differed only by case.
- Fixed selection jumping to the wrong item after filtering with no prior selection.
- Fixed encoding for values containing quotes in CSV Export.
3.0.7-alpha
You can now specify the Access level of Project-level documents:
Removed the "Field Changes" section in the Project:Archive tab.