All Projects → EntCollNet → BugFlow

EntCollNet / BugFlow

Licence: CC0-1.0 License
Bug flow is a community resource for entomological collection digitization workflows and modules.

Programming Languages

HTML
75241 projects
CSS
56736 projects

Projects that are alternatives of or similar to BugFlow

depsbot
⚙️ GitHub action to check freshness of your deno dependencies
Stars: ✭ 28 (+55.56%)
Mutual labels:  best-practices
thesis template
A comprehensive LaTeX template with examples for theses, books and more, employing the 'latest and greatest' (UTF8, glossaries, fonts, ...). The PDF artifact is built using CI/CD.
Stars: ✭ 121 (+572.22%)
Mutual labels:  best-practices
HacktoberFest-21
A mentorship initiative to help beginners kickstarting their open-source journey by completing Hacktoberfest'21 challenge | Curated list of beginner-friendly issues for Hacktoberfest 2021 | Raise PR to add your issues
Stars: ✭ 27 (+50%)
Mutual labels:  best-practices
theBookOfNoah
Everything ive learned developing web applications
Stars: ✭ 22 (+22.22%)
Mutual labels:  best-practices
CSharpHandbook
The focus of this document is on providing a reference for writing C#. It includes naming, structural and formatting conventions as well as best practices for writing clean, safe and maintainable code. Many of the best practices and conventions apply equally well to other languages.
Stars: ✭ 25 (+38.89%)
Mutual labels:  best-practices
firecracker
Stop half-done API specifications! Cherrybomb is a CLI tool that helps you avoid undefined user behaviour by validating your API specifications.
Stars: ✭ 438 (+2333.33%)
Mutual labels:  best-practices
Y-BP
YFE Team 前端最佳实践
Stars: ✭ 28 (+55.56%)
Mutual labels:  best-practices
programing-best-practices
A curated list of awesome Programming Best Practices For Good Developer 🥰
Stars: ✭ 67 (+272.22%)
Mutual labels:  best-practices
symfony-lts-docker-starter
🐳 Dockerized your Symfony project using a complete stack (Makefile, Docker-Compose, CI, bunch of quality insurance tools, tests ...) with a base according to up-to-date components and best practices.
Stars: ✭ 39 (+116.67%)
Mutual labels:  best-practices
BestPracticesWorkshop
Repository for the workshop "Best practices on development"
Stars: ✭ 14 (-22.22%)
Mutual labels:  best-practices
Clean-Architecture-Template
Configurable Clean Architecture template containing the DDD + CQRS approach for .NET Core applications.
Stars: ✭ 14 (-22.22%)
Mutual labels:  best-practices
PackageProject.cmake
🏛️ Help other developers use your project. A CMake script for packaging C/C++ projects for simple project installation while employing best-practices for maximum compatibility.
Stars: ✭ 48 (+166.67%)
Mutual labels:  best-practices
inventory
UNICEF Open Source Inventory. A UNICEF Global Innovation knowledge base of best practices and resources for working and leading Open.
Stars: ✭ 23 (+27.78%)
Mutual labels:  best-practices
torinotech.github.io
torinotech.github.io
Stars: ✭ 16 (-11.11%)
Mutual labels:  best-practices
data-science-best-practices
The goal of this repository is to enable data scientists and ML engineers to develop data science use cases and making it ready for production use. This means focusing on the versioning, scalability, monitoring and engineering of the solution.
Stars: ✭ 53 (+194.44%)
Mutual labels:  best-practices
basetemplate9
TYPO3 v9 LTS Template Foundation - Use it as a base for your website configuration. Add all your Stylesheets, JavaScripts and Templates.
Stars: ✭ 15 (-16.67%)
Mutual labels:  best-practices
Software-Component-Verification-Standard
Software Component Verification Standard (SCVS)
Stars: ✭ 82 (+355.56%)
Mutual labels:  best-practices
django-yadpt-starter
Yet Another Django Project Template skeleton for Django projects
Stars: ✭ 28 (+55.56%)
Mutual labels:  best-practices
BetterRepository
Better Enhanced Repository Pattern Implementation in .NET C#
Stars: ✭ 27 (+50%)
Mutual labels:  best-practices
Surf-iOS-Developers
Основной репозиторий iOS команды Surf
Stars: ✭ 110 (+511.11%)
Mutual labels:  best-practices

BugFlow

Bug flow is a community resource for developing and sharing entomological collection digitization workflows and modules. Plans are to capture the methods and practices used to do this work and incorporate new versioning and metadata practices for workflows developed using these modules. If time allows, include some exemplar digitization workflows that were built from these new modules and incorporating the new metadata information and publishing them in several formats (PDF, DOCX, TXT). To support wider adoption and ease-of-use, the group will endeavor to produce versions in multiple languages.

About BugFlow

See the About BugFlow page to learn about our history and project members.

Get involved with BugFlow!

BugFlow on Slack

We work together, develop ideas, and stay in touch on the BugFlow Slack, we would love to have you join us.

Collaborate on building modules and workflows

We are always looking to grow our team of contributors and value community feedback. Join slack or send an email to any members of BugFlow to get connected. Please leave feedback requests and discussion in our Project Issues tracker.

Have an existing workflow from your institution to deposit? Submit a link to a workflow or create a new workflow from scratch in our Workflow Creator

BugFlow Modules

The primary output of BigFlow is a set of modules that outline the tasks and resources needed to create digitization workflows for entomological collections. They are actively being developed within this repository, and are available here:

Current BugFlow Modules

To see issues and tasks still pending, please see the github repository issues located here: BugFlow Issues

Modules are currently being updated. The following map shows how the modules relate to each other and might fit into a collection-specific set of workflows.

Map of digitization modules

BugFlow is broken into 5 super-modules which are linked below. Each super-module is broken down into constituent submodules that focus on specific tasks related to digitizing particular types of objects contained in entomological collections.

Super-Module 1 - Pre-digitization Curation (Staging) | Super-Module 2 - Project Management | Super-Module 2 - Label Data | Super-Module 4 - Imaging | Super-Module 5 - Value-added

Exemplar workflows

As the modules are developed, examples of workflows containing incorporating these modules will be given here.

If you have a workflow to contribute or deposit into Bugflow, use the corresponding "Workflow Template" here

Entomological Collections Best-Practices

Several members of the BugFlow project have joined with other individuals from the entomological collections community to work on entomology-related Best Practices for the SPNHC wiki, see: SPNHC Best Practices. Contact anyone from BugFlow to get connected with that project.

Legacy Modules

A series of modules were developed through the coordination of iDigBio in 2013. Information about these modules, upon which BugFlow was based, can be found here.

Digitization in context

Understanding why we digitize our collections objects drives the elements of a successful workflow. We digitize our collections for three broad reasons:

  • our own internal uses of collections management,
  • intra-community access to collections data without requiring an in-person visit
  • mobilize and make available collections data to external research, policy, and education initiatives

See public page here Bug Flow

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].