Giter Site home page Giter Site logo

catalogueoflife / checklistbank Goto Github PK

View Code? Open in Web Editor NEW
6.0 6.0 2.0 5.47 MB

UI for checklistbank.org

Home Page: https://www.checklistbank.org/

HTML 0.13% CSS 0.59% JavaScript 99.28%
taxonomic-classifications taxonomies taxonomy taxonomy-database taxonomy-management

checklistbank's People

Contributors

gdower avatar mattblissett avatar mdoering avatar thomasstjerne avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Forkers

gustibimo dhobern

checklistbank's Issues

Discuss how to best show synonyms

Synonyms need to expose their status and accordingTo in case of misapplied names. Status is missing from the Synonymy object currently.

And heterotypic synonyms might better not be labeled as such. Its a catch all. Only homotypic synonyms are clearly homotypic and should be shown as such.

Col Source form - input from @yroskov

Please rearrange them as I present below:

  • [Please add field] “Source ID” (A unique ID assigned to the dataset by the CoL software).
  • “Title” to “Full Name” (Full title of Source Database, as it is supplied by the custodian)
  • “Alias” to “Short Name” (Abbreviated or shortened memorable name of Source Database intended for easy use in day-to-day communications, as supplied by the custodian)
  • “Version” (Number or code, plus date, where Month and Year are obligatory) provided by the custodian; style specified by the CoL editor and custodian of Source Database)
  • “Released” to “Release Date” (Original date (Year-Month-Date) of issue of the version for the Catalogue of Life).
  • “Authors and editor” to “Authors/Editors” (Name(s) of Source Database editor or author; as specified by the custodian).
  • “Coverage” to “Taxonomic Coverage” (Higher taxa, which represent taxonomic position of sector(s) covered by the database in the classification). This field should be filled automatically after database sectors attached in the Tree.
  • “Group” to “English name of the group” (English name of the taxon covered by the Source Database).
  • “Description” to “Abstract” (Standardised short database description (text of 80-90 words) for use in the Catalogue of Life and supporting materials, such as the booklet published with the Annual Checklist).
  • Organization (Name of the Organisation that hosts the Source Database).
  • Home Page (Internet address of the project/resource website).
  • “Citation” to “Bibliographic Citation”. This field should be filled by the software. Bibliographic citation should be generated from Authors/Editors, Year of the product, GSD name “as displayed”, “Version” and selected CoL metadata.

Please add fields:

  • “Is new?” [values: 0=untouched, 1=new in a year cycle, 2=updated in a year cycle] (A flag for new and updated databases in a year cycle)
  • “Coverage” [values: Global, Regional] (Geographic coverage of the Source Database for the taxon)
  • “Completeness” [values: 1 to 100%] (Percentage of completeness of species list of the taxon provided by the Source Database)
  • “Checklist Confidence” [values: 1, 2, 3, 4, 5] (Quality of taxonomic checklist with values 1 to 5; quality is stated by the custodian in agreement with CoL editor. Confidence indicators are described at http://www.catalogueoflife.org/col/info/databases).
  • “Editor’s comments” [this field is new; it was not implemented in old structure. Perhaps later it should be extended into number of fields with management information].

less navigation menus?

we have a top n side menu, tabs and a breadcrumb which often show very much the same. Can we reduce this without sacrifycing functionality? maybe we can reserve the sidebar for actions, stats or faved items?

Sector comparison view

Visualizing changes between different sector sync attempts should assist the editorial work a lot. The API is providing two ways of comparing different versions of a sector:

TextTree
A indented, simple text tree representation including synonyms for the entire sector is part of the SyncImport metrics we generate for every sync attempt. The API offers a diff service between any two successful attempts which can be rendered as a markdown table. We can easily change the representation or even allow to ask for different formats (e.g UnifiedDiff, Markdown, Html)

http://api-dev.col.plus/assembly/3/sync/210/treediff?attempts=7..9

NameIndeIds
Also the complete set of NameIndexIds for all names is included.
The API will offer a diff between any 2 attempts which could be visualised in a simple (potentially large) table.

http://api-dev.col.plus/assembly/3/sync/210/namesdiff?attempts=7..9

Show homotypic names and name relations on name page

We should not show "Homotypic Name Id", but instead list all homotypic names via the call:
/dataset/{dkey}/name/{id}/synonyms

Also show the publication and all name relations:
/dataset/{dkey}/name/{id}/relations
/dataset/{dkey}/name/{id}/publishedIn

Modify MC

Add child
Del child
Change name lookup via names index

Manage imports

List currently running and queued imports.
Allow to cancel running or queued imports and schedule new ones

Customise columns

Default settings based on issue types
User defined, save in localStorage, maybe persist to GBIF user later

Design simple landing page

There should be a Clearinghouse landing page when fist visiting the site.
Ideas to show:

  • short paragraph what the site is about
  • key numbers with links (num datasets, num names index names, num taxa/names in CoL draft)
  • latest dataset(s) added and imported

Filter datasets by catalogue

Allow dataset table to only show datasets for the scrutinized or provisional cat.

@yroskov Maybe rename the rendered value to "pCat" and "sCat" or "CoL" and "prov CoL"

Action buttons in table

Actions:

  • Block name
  • Change status (Accepted name, Ambiguous synonym, Misapplied name, Prov accepted name, synonym)
  • No action

show taxon/name link URL

A plain name, taxon or synonym can have a link property that takes a URL to its "homepage" in the original source. Show that link on a taxon/synonym/bare names page

About page

There should be an about page describing the purpose of the site in more detail.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.