Skip to content
This repository was archived by the owner on Nov 21, 2022. It is now read-only.
This repository was archived by the owner on Nov 21, 2022. It is now read-only.

Identify the most important fields in the directory-data regarding futuresque queries/requests  #5

Description

@mukil

Query API Freifunk Community Model

The following listing (extracted from the summarized-json dump) hierarchically informs us about (data) fields which are available in the ffn-directory-api but which the dm4-freifunk-api plugin has not yet (A) mapped to types and therefore is (B) not yet processing it.

Now it would be helpful to get to know (from potential users) which are the most important data-fields (regarding useful queries/usage-scenarios) when looking through the following list of items:

  • Timeline (Timestamp, Description)
  • Contact (Mailinglist, Twitter, Facebook, IRC, E-Mail, Identica, Google+)
  • Status (Message, Last change, Node Number, Focus Topics)
  • Location (Latitude, Longitude, Country (either "Germany" or "DE"), City, Address (Street, Name, Zipcode))
  • More Tech Details (Bootstrap, Key exchange, Splashpage, Top level domain || DNS (Domain name, Nameservers), Störerhaftung)
  • Services (Internal URI, Service Name, Service Description) - see Halle
  • Nodemaps (URL, Interval, Technical Type, Map Type)
  • Feeds (Category, URL, Type, Name)
  • Metacommunity Name
  • Events (Extra Info) - see Wiesenburg
  • Support (Donations (Campaigns (Project ID, Provider)))

Glad for your feedback & Cheers!

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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