1. If you are here for the first time, welcome to the beginning world of Skooppa.

    And more importantly, thanks for being here!

    Please keep in mind we are just starting, so a lot of questions might not be answered in great detail and to your satisfaction. Please be assured, this situation isn't something we are happy about, as we want to be as transparent as possible as a company. However, we can't give up all our innovative ideas, before we actually make them real. We need to keep a competitive advantage. Be rest assured though, our ideas are really cool, innovative and we have a lot of them.

    So with that having been said, we invite you to join our cause and thank you again for doing so. We know that it is you, who will make Skooppa great.

    The Skooppa Team! Oh, and please don't forget to register. This big notice will disappear, once you do!
    Dismiss Notice

The data object - a core component to Skooppa's data modeling system

Discussion in 'Platform Concepts' started by s.molinari, Dec 21, 2013.

  1. s.molinari

    s.molinari Uber Dreamer Staff Member Adreamistrator

    We are now embarking on testing technologies to support Skooppa's data object system.

    A Data Object is basically the website owner's / admin's/ developer's basic component in the model part of the MVC architectural foundation in Skooppa. It gives him or her the ability to manipulate the model at will.

    The preliminary field types in data objects will be the following (and this list may change moving forward).

    Auto Number
    A system-generated sequence number that uses a display format you define. The number is automatically incremented for each new record.

    Image
    So a single title image or representative image can be uploaded. It will be also accessible through Skooppa's media management system.

    Formula

    A read-only field that derives its value from a formula expression you define. The formula field is updated automatically, when any of the source fields change.

    Master-Detail (one-to-many)
    This is important, when data hierarchies and ownership need to be followed. For instance, if a master data record is deleted, all detail records will be deleted too.
    Lookup Relationship (one-to-many)
    Creates a relationship that links this object to another object. The relationship field allows users to click on a lookup icon to select a value from a popup list. The other object is the source of the values in the list.

    Lookup Relationship (many-to-many)
    Creates a relationship that links this object to another object. The relationship field allows users to click on a lookup icon to select a value from a popup list. The other object is the source of the values in the list.

    Roll-Up Summary
    A read-only field that displays the sum, minimum, or maximum value of fields, which can be aggregated, from a related object or it can be the record count of all records from a related object.

    Checkbox
    Allows users to select a True (checked) or False (unchecked) value.

    Date
    Allows users to enter a date or pick a date from a popup calendar.

    Date/Time
    Allows users to enter a date and time, or pick a date from a popup calendar. When users click a date in the popup, that date and the current time are entered into the Date/Time field.

    Email
    Allows users to enter an email address, which is validated to ensure proper format. If this field is specified for a contact or lead, users can choose the address when clicking Send an Email. Note that custom email addresses cannot be used for mass emails.

    Address
    Allows users to enter an address and it formats according to the country selected. It also automatically holds picklists like the states for USA or regions for Germany (i.e. Rheinland-Pfalz, Bayer, etc.) and this for every country in the world.

    Currency
    Allows users to enter a dollar or other currency amount and automatically formats the field as a currency amount. This can be useful if you export data to Excel or another spreadsheet.

    Geolocation
    Allows users to define locations with latitude and longitude values.

    Number
    Allows users to enter any number. Leading zeros are removed. Possible to also be used for external IDs, with automatic duplication checking.

    Percent
    Allows users to enter a percentage number, for example, '10' and automatically adds the percent sign to the number. "10" will also translates to the value ".10" in a formula field.

    Phone
    Allows users to enter any phone number. Automatically formats it as a phone number.

    Picklist
    Allows users to select a value from a list you define.

    Picklist (Multi-Select)
    Allows users to select multiple values from a list you define.

    Text
    Allows users to enter any combination of letters and numbers.

    Text Area
    Allows users to enter up to 255 characters on separate lines. Possible to also be used for external IDs, with automatic duplication checking.

    Text Area (Long)
    Allows users to enter up to 32.768 characters on separate lines.

    Text Area (Rich) (the WYSIWYG editor and heart of external content creation)
    Allows users to enter formatted text, add images and links.

    Text (Encrypted)
    Allows users to enter any combination of letters and numbers and store them in encrypted form.

    URL
    Allows users to enter any valid website address. When users click on the field, the URL will open in a separate browser window. (possible make this optional to opening in the same window?)

    All of the fields will have automatic validation for their types. For instance, the email field will automatically check to make sure it is a valid email format. I.e. text@text.tld

    One of the hurdles we are working on is basically breaking the schema mold of an RDBMS. It is a known fact that unfortunately, MySql Cluster, despite its relatively new online schema update system, is just not a happy camper, when the schema is changed too often. We need to get around this in a serious way, because we do want customers to change their data model at will, without any real performance side effects. That is a tricky situation and one which needs a lot of thought and concentration.

    To that effect, we are looking at an inverted indexing solution often used for searching databases to make basically an SQL system into a No-Sql system. We will be simply trying out the theory to see how well it will work and to determine, if it is a proper solution for our free-for-all Skooppa data model. :)

    Some might be asking, why not just use a No-Sql database? Well, we just might. We haven't decided this yet and these are simply our first tests.:) Our only concern is true ACID compliance, (which even the inverted indexing can cause issues with, which we must accommodate for).

    At any rate, at the same time, we are going to be creating a working mock-up of the data object management system. Those are our first two main goals.

    Scott
     
  2. Matbret

    Matbret New Member

    Cialis Online Toronto Real Dutasteride Duprost Low Price In Us Semen Infection Amoxicillin
     

Share This Page