User:Emilio/Porting
Porting is the term we use on Appropedia to describe the adaptation of knowledge from different sources into our in-house format, which
This guide will describe what can be ported, how to port
What can be ported
[edit | edit source]- It aligns with Appropedia's mission
- Open licensed
- It can be adapted
- May use multiple formats such as video
- Originally localized
- Can be old
- Licensing
- What we accept
- Grey area
- Not accepted
- Releasing
- Subject matter
- What we want on Appropedia
- What we don't want on Appropedia
- Personal information
- Low-quality images
- Anything that breaks our Appropedia:Terms of use
- How to assess feasibility
- Preparing sources
- PDF
- OCR
- How to process
- TXT
- HTML
- PDF
- Metadata
- Predefining a structure
- Normalizing to our properties
- Preserving as much as possible
- Extracting metadata
- Manual review
- Using an LLM
- Other ways (keyword matching, fuzzy matching, etc.)
- Methods
- Manual editing
- Worth the effort if small dataset
- Batch importing
- Editing txt files and using a maintenance script
- Building wikitext from a spreadsheet
- Using the MediaWiki API
- Manual editing
- Good practices
- File structure: we prefer a single portal with projects as subpages
- Naming: we strive to follow our Appropedia:Page naming recommendations
- Batch editing: reviewing the external source of truth (e.g. a spreadsheet) to reduce multiple changes and revisions.
Personal tools
- Design files audit: https://github.com/dubsnipe/manufacturing-file-auditor
- Semantic tagger: https://github.com/dubsnipe/semantictaggR