Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

API Changes:

  • AN-2220: All the filters in the asta requisition should be same.

    1. Previous Endpoint: `/api/workflow?organizationId=1`
   - Current Endpoint: `/api/workflow?organizationIds=1,2`
   - Explanation: In the previous version, this endpoint retrieves workflow data for an organization with ID 1. In the current version, it's updated to retrieve workflow data for organizations with IDs 1 and 2, allowing data retrieval for multiple organizations simultaneously.


2. Previous Endpoint: `/api/customer?organizationId=1`
   - Current Endpoint: `/api/customer?organizationIds=1,2,3`
   - Explanation: Similar to the workflow endpoint, the previous version retrieves customer data for an organization with ID 1. In the current version, it's modified to fetch customer data for organizations with IDs 1, 2, and 3, accommodating multiple organizations.


3. Previous Endpoint: `/api/requisition/getAllRequisition?location=RA&stateId=1&firstItemStateId=1&typeId=1`
   - Current Endpoint: `/api/requisition/getAllRequisition?locations=RA&stateIds=1&firstItemStateIds=1&typeIds=1,2`
   - Explanation: This endpoint retrieves all requisitions with specific location, state, first item state, and type IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`, `firstItemStateId` to `firstItemStateIds`, `typeId` to `typeIds`), allowing for multiple values for each parameter.


4. Previous Endpoint: `/api/requisition/requisitionItems/{requisition_id}?location=RA&stateId=1`
   - Current Endpoint: `/api/requisition/requisitionItems/{requisition_id}?locations=RA,RH&stateIds=1`
   - Explanation: This endpoint retrieves requisition items for a specific requisition ID, with specific locations and state IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`), allowing for multiple values for each parameter.


5. Previous Endpoint: `/api/export/requisitions/print-items?location=RA&stateId=1&firstItemStateId=1&typeId=1`
   - Current Endpoint: `/api/export/requisitions/print-items?locations=RA&stateIds=1&firstItemStateIds=1&typeIds=1,2`
   - Explanation: Similar to the `getAllRequisition` endpoint, this endpoint exports requisition items with specific location, state, first item state, and type IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`, `firstItemStateId` to `firstItemStateIds`, `typeId` to `typeIds`), allowing for multiple values for each parameter.

Highlights:

AN-2171: Improve search UI

AN-2295: New search: Make the selection of filters modal/pop-up

AN-1981: Move preferences from MongoDB to Postgres

AN-1954: Implement batch correction from Asta Online in Asta7

AN-2213: Restricted access to a non-root object

AN-2210: Enable printing QR-kodes for archive entities in the same menu as printing labels

AN-2206: Show storage locations when viewing a storage room

AN-2205: "Load all" racks does not work

AN-2191: Restricted user unable to create new archive entities

AN-2190: Validation data correction bug

AN-2182: Template preference is not working in asta7.

AN-2181: Import is not working in the asta-requisition.

AN-2112: Get rid of spring data rest from asta repository

AN-2080: Access to repository for Asta 7 users

Tasks:

AN-2295: New search: Make the selection of filters modal/pop-up

AN-2277: System entity preference issue in migration data

AN-2245: Add Danish translation to the shelf marker

AN-2238: Persists all toast messages before page reload

AN-2236: R&D : We've hardcoded secretData and salt for user credentials in archive-manager.json.

AN-2228: As an Asta 7 administrator I want to keep logs over who logged into Asta 7 to be able to follow up on information security

AN-2221: Translations - Repository

AN-2215: Publishing digital-files to the portal

AN-2212: ISAD(G) make it possible to search in a range of start and end date for entities

AN-2210: Enable printing QR-kodes for archive entities in the same menu as printing labels

AN-2206: Show storage locations when viewing a storage room

AN-2204: Translation repository

AM-271: Use actuator/prometheus disk metrics for disk usage alert

AN-2203: R&D: Add azure service discovery in prometheus

AN-2199: Verify that the installation instructions for Direct HTTPS still works after non-root user running the container

AN-2196: Requisition project migration from JavaScript to Typescript

AM-269: Create and send an alert if any Asta7 is not healthy

AN-2171: Improve search UI

AN-2136: Pagination Option For Storage Unit View on Details of Repository Page (rack, shelf, bay,etc)

AN-2112: Get rid of spring data rest from asta repository

AN-2101: Move notification pop-ups away from the top right

AP-715: Restrict access to the Try Portal

AN-2080: Access to repository for Asta 7 users

AN-2056: R&D on how to make use of blob storage

AN-1981: Move preferences from MongoDB to Postgres

AN-1954: Implement batch correction from Asta Online in Asta7

AN-1616: Add spesific keybind for "lag og legg til søsken" when creating units

AN-1398: Code refactoring for "archive report in excel format"

Bugs:

AN-2294: Unable to search using a non-standard template

AN-2272: It is not possible to search for space in more than the 20 first store rooms

AN-2268: Showing wrong date in shelf marker for portal requisition

AM-275: Find root cause of "Waiting queue of [read] pool is exhausted. Please try again later."

AN-2244: Unable to search for storage location in racks higher than 0020

AN-2226: Portal publis gives "status":500,"error":"Internal Server Error","message":"HV000090: Unable to access getPeriod.","path":"/api/archive-unit/publish"}

AN-2225: Storage location update is not working

AN-2237: When root title is too long then the sync job fails.

AN-2222: The Word based archive list (Export archive) in Asta 7 reverses the dates on the list

AN-2217: Show in tree places objects under the wrong archive in the archive tree

AN-2213: Restricted access to a non-root object

AN-2209: Unable to delete unresolved storage objects due to shelf space issue

AN-2207: Print archive information on rack level does not work

AN-2205: "Load all" racks does not work

AN-2202: Filename/filelink in file-object without thumbnails is not displayed correctly

AN-2191: Restricted user unable to create new archive entities

AN-2190: Validation data correction bug

AN-2183: Saved quick search have all entities selected, even though only one entity was initially chosen

AN-2182: Template preference is not working in asta7.

AN-2181: Import is not working in the asta-requisition.

AN-2169: Unable to do open in a new tab functionality for newly added participants.

AN-2150: Export single archive from GUI doesn't work

AN-2127: The user should be able to delete all the orphan storage units.

AN-2270: Pagination is not working in the portal requisition.

ASYN-98: Fix handling empty string for period precision while publishing

Stories:

Tasks with note:

  • AN-2229: Optionally make it possible keep all requests to Asta 7 in a log on disk

    For adding custom nginx log in data disk, we need to follow below steps

    • First create folder in /data with name asta7_nginx_log

    • Initially the ownership of the folder will be root, we must change the ownership to user otherwise gui-pt will not work

    sudo chown -R $(whoami):$(whoami) /data/asta7_nginx_log

    • in the docker-compose we already have volume mount in gui-client which will mount this folder to container and we will have log in data disk 

      volumes:
      - ~/.asta7-ssl:/etc/nginx/ssl
      - /data/asta7_nginx_log:/var/log/nginx

    • for rotating log of nginx in data disk we will use logrotate in linux, to setup this follow below command

    sudo apt install logrotate
sudo nano /etc/logrotate.d/asta7

/data/asta7_nginx_log/*.log {
        weekly
        compress
        create 0640 ubuntu ubuntu
        copytruncate
        dateext
        su root adm
        missingok
        notifempty
}

# to spot our logrotate configuration
sudo logrotate /etc/logrotate.conf --debug

# to Test without waiting
sudo logrotate -f /etc/logrotate.d/asta7

# in the "/data/asta7_nginx_log/" we will find backup file of the log and original file become empty

  • AN-2220: All the filters in the asta requisition should be same.

    1. Previous Endpoint: `/api/workflow?organizationId=1`
   - Current Endpoint: `/api/workflow?organizationIds=1,2`
   - Explanation: In the previous version, this endpoint retrieves workflow data for an organization with ID 1. In the current version, it's updated to retrieve workflow data for organizations with IDs 1 and 2, allowing data retrieval for multiple organizations simultaneously.


2. Previous Endpoint: `/api/customer?organizationId=1`
   - Current Endpoint: `/api/customer?organizationIds=1,2,3`
   - Explanation: Similar to the workflow endpoint, the previous version retrieves customer data for an organization with ID 1. In the current version, it's modified to fetch customer data for organizations with IDs 1, 2, and 3, accommodating multiple organizations.


3. Previous Endpoint: `/api/requisition/getAllRequisition?location=RA&stateId=1&firstItemStateId=1&typeId=1`
   - Current Endpoint: `/api/requisition/getAllRequisition?locations=RA&stateIds=1&firstItemStateIds=1&typeIds=1,2`
   - Explanation: This endpoint retrieves all requisitions with specific location, state, first item state, and type IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`, `firstItemStateId` to `firstItemStateIds`, `typeId` to `typeIds`), allowing for multiple values for each parameter.


4. Previous Endpoint: `/api/requisition/requisitionItems/{requisition_id}?location=RA&stateId=1`
   - Current Endpoint: `/api/requisition/requisitionItems/{requisition_id}?locations=RA,RH&stateIds=1`
   - Explanation: This endpoint retrieves requisition items for a specific requisition ID, with specific locations and state IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`), allowing for multiple values for each parameter.


5. Previous Endpoint: `/api/export/requisitions/print-items?location=RA&stateId=1&firstItemStateId=1&typeId=1`
   - Current Endpoint: `/api/export/requisitions/print-items?locations=RA&stateIds=1&firstItemStateIds=1&typeIds=1,2`
   - Explanation: Similar to the `getAllRequisition` endpoint, this endpoint exports requisition items with specific location, state, first item state, and type IDs. In the current version, the parameters are pluralized (`location` to `locations`, `stateId` to `stateIds`, `firstItemStateId` to `firstItemStateIds`, `typeId` to `typeIds`), allowing for multiple values for each parameter.

  • AN-2138: Include created field when migrating content from Asta 5 to Asta 7

    1. Use below query to export archive units created field value and save it to a file such as archive-unit.csv

    select ARKIVENHET.ENHETSTYPEENHETSTYPEID, ARKIVENHETURN.URN, ARKIVENHET.OPPRETTETDATO, ARKIVENHET.OPPRETTETAV from ARKIVENHET
inner join ARKIVENHETURN
on ARKIVENHET.ARKIVENHETID = ARKIVENHETURN.ARKIVENHET_ARKIVENHETID;


    2. Use below query to export archive units created field value and save it to a file such as

    aktor.csv

    select AKTORURN.URN, AKTOR.OPPRETTETDATO, AKTOR.OPPRETTETAV from AKTOR
inner join AKTORURN
on AKTOR.AKTORID = AKTORURN.AKTOR_AKTORID;


    3. Run the following script after replacing

    ARCHIVE_UNIT_FILE, AKTOR_FILE and PROJECT_ID variable value.


  • AN-1943: Improve search to include member and system entities 

    Need to re-index all the initialized projects (based on settings it might take some time to finish).

Changes made in the Participant Module settings
    Only the Aktor entity is searchable.
    The rest of the entities are part of the Aktor entity.

Changes made in the ISAD(G) entity settings
    Only the main entities (Arkiv, Arkivdel, Serie, Stykke, Mappe, Aksesjon, Tilvekst) are searchable.
    The rest of the entities are part of the main entities.

Possible consequences on the saved searches due to the changes made
  As the basic search filter now supports a single project only, any saved search having multiple projects will no longer work.
  Any saved search made using the entities that are no longer searchable will not work.

Install-Package:

How to upgrade:

  1. Stop the previously running Asta7

    cd previous_asta7_directory
docker compose down

  2. Download and extract Asta7 1.63.0

  3. Adjust the .env file according to the previous one

  4. Run Asta7 1.63.0

    cd asta7-1.63.0
docker compose up -d

  5. Regenerate the requisition client secret from Keycloak

  6. Put the new client secret in .env and restart Asta7 

    docker compose restart

7. Re-index search data for all the initialized projects.

Configuration:

  • No labels