Auctions – data model, refresh and limitations

Overview

Browser for MBVK (court bailiff) auctions: list with images, attributes, bids and bailiff; interest marking, recommendation e-mail and manual refresh from the MBVK API.

Data model

Table names carry the installation's own prefix in the database.

Endpoints

• mbvk.statusexclude, mbvk.statusinclude: interest status 0 or 1 (updateAuctionInterestStatus).
• mbvk.sendrecommendation: recommendation e-mail to one address via the central mailer, in immediate mode.
• mbvk.manualbidupdate: manualFullUpdate() — calls the MBVK detail API and rewrites attributes and images.
• mbvk.imageproxy: downloads images only from the mbvk.hu host; only checks that the session token matches.
• mbvk.map: opens the MBVK layer of the map; the permission is checked by the map module.

Background job

From the framework's cron list, the cron/mbvk entry point calls task/mbvk.run: fetches list, details and bids, protected by a lock file.

Permissions

• The additional endpoints (except imageproxy) check the basic modify right. The controller does not check the list permission of the list.
• map: install/permission_market_map_v1.sql.

Known limitations

• The form, save and delete behind the header + button are copied code: they edit a label on the label model; delete calls the method getTotalCompaniesByCompanyGroupId, which does not exist on the label model.
• The format check of the recommendation e-mail address is disabled in the code. The test endpoint sendrecommendation23232 sends to the store address with PHP mail(); imageproxy22 is a second image proxy.
• There is no endpoint for the statusdelete key; add and debug are not classified in the seeds.
• On the Hungarian interface the interest button reads "Kamat" (translation error).