Libraries tagged by Data Cleaning

A library for creating simple data models.

Go to Download

A collection of helpers for creating abstractions of data models in PHP.

Go to Download

CakePHP Fixtures plugin to read fixtures and creating tables with data from tests

Go to Download

Works with data which could be helpful during creating system.

Go to Download

Builder task for quickly creating a shop with dummy data

Go to Download

This PHP class that extracts image tags from HTML code and allows keeping a record of the processed images in a data structure such as a database, creating an abstraction layer that allows the user handle its web application images. The main reasons you would do this are saving up disk space and SEO.

Go to Download

Survloop is an open data engine for designing a database and creating a mobile-friendly user interfaces to fill it.

Go to Download

Module for creating and updating static content using data scripts.

Go to Download

Creates a webhooks that make end to end or manual testing of Laravel apps easier. Allows creating db snapshots and changing app date.

Go to Download

Base templates utilizing Livewire and Tailwind for Creating, Retrieving, Updating, and Deleting (CRUD) data for administering your Laravel site.

Go to Download

Survloop is an open data engine for designing a database and creating a mobile-friendly user interfaces to fill it.

Go to Download

This module [1] Adds translation data from [module or theme root]/i18n/Js/[locale].csv to frontend translation dictionary. [2] Enables Module to override Theme, Language Pack and DB translations by creating CSV file in specific location inside the Module.

Go to Download

This documentations describes what the GeoAPI is and how to use it properly. **What is GeoAPI** The GeoAPI allows DPD customers to manage (CRUD) their shipments and shipment related data. The main purpose of the API is to provide the customer the means for: - Creating and managing new shipments - Ordering pickups for parcels - Printing parcel labels - Listing all available shipping services - Validating shipping routes It also provides methods for listing your pickup addresses and the details of individual parcels. Each user is assigned a user account under which he is able to track multiple customer DSWs (customer numbers). You as a customer can use a single GeoAPI account to send shipments under multiple DPD customer numbers.

Go to Download

A package for creating a General user entity, with the ability to save his actions in the application before authorization and subsequent linking of the received data with the authorized user.

Go to Download

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download