Skip to content

function organizing and naming #7

@sformel

Description

@sformel

I got thinking about consistency of our functions and the IPT. I'm partly influenced by the tidy philosophy.)

  1. I propose we rename our current functions to organize them into families.
  2. I propose we remove ipt from any function names (this is implicit in the module)
  3. I propose we replace project with resource as that is what the IPT devs use. See the manual glossary for resource definition.

open_ipt_session --> session_open
create_new_ipt_project --> resource_create
refresh_ipt_project_files --> resource_refresh_files
refresh_ipt_project_metadata --> resource_refresh_metadata
change_publishing_org_ipt_project --> resource_change_publishing_org
make_public_ipt_project --> resource_make_public
publish_ipt_project --> resource_publish
register_ipt_project --> resource_register_with_GBIF
add_network_ipt_project --> resource_add_network
check_if_project_exists --> resource_exists

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions