Integrating with Sentral - multiple incidences, one school - integration

Integrating with Sentral for a school that has multiple incidences to reflect multiple campuses
Would it be possible to pull all this information into a data lake from across the four campuses and then use the Clipboard database connector to integrate?
Wonde doesn't work for a school with multiple incidences

Related

I want to create a service that allows my company's products to move pages only for the products that customers have

This article was written using a translator.
There are many products in my company.
Like Atlasian, I want to create a service that allows my company's products to move pages only for the products that customers have.
In order to do so, you need to know the products of each customer, and I need to make sure that only those products can be clicked, but can you not use the database?
Using the database makes it so complicated that I want to implement it as simple as possible.
You need to know a programming language/ framework that allows you to create a service/api.
There are various ones available.
Search on the internet.
The architecture of a service is slightly different from directly having a data entry form that stores into a database.
Most apis'/ service entails you creating classes to do CRUD operations(i.e create,read,update and delete operations) by coding classes and then consuming the API into the application.
So yes you can have within the API classes that can be called and then used to store information that the customer has installed into a database, and also retrieve product values specific to a specific customer.
See API as mid layer between front end,and database

Follow Up Customer Database Design

Please excuse me if this isn't the traditional format of how questions are asked or if it is too broad.
I am currently looking for suggestions on how to design and build a customer database with some very simple fields. I work in the sales department for a company that retails after-market truck accessories both online and over the phone. I have some basic programming skills and a little technical ability, the goal of this project is to create a method of targeting sales leads we would like to follow up with.
We will be collecting information from the salesman individually, I imagined creating a web portal that allowed them to answer the following questions:
Customer Email?
How did they find us?
The website they called in on.
Year of the Vehicle?
Make of the Vehicle?
Was the initial investment < $750.00?
Date of purchase?
I would like to query and target customers based on those questions I have listed above.
Any suggestions or insight would be very much appreciated.
-Luke
You have to face a three-stage process:
First Step: Collect all the information you need to include in your database. You can collect this information from people or documents.
Second Phase: Develops a relational database model that allows you to manage the information according to the first 3 formalization rules. If the database is used by external users, you should designs queries and forms to facilitate their work.
Third Phase: Make your own database. If you do not have a software yet, look for one that supports the relational model. Have you already tried MS access?

Build a social network & organization database

I'm doing a PhD in political science and plan to collect datas on several organizations and do some social network analysis.
I'm new to database building and management, and I'd like to know what tool (LibreOffice Base, MySql, etc.) would be the best for me.
In this database, I would have a list of organizations (approximately 200) with various attributes and files attached, a list of individuals working in/with one or several of these organizations, a list of coalitions linking different organizations, a list of events where some organizations/individuals are, etc.
I'm starting from scrap, what do you think would be the best way to build this database ? I tried with LibreOffice Base and started to create different tables (organizations, individuals, etc.) but I'm not sure it will fit my needs.
Thanks in advance !
I think you should look at a graph database engine like Neo4J for this use case.
With a graph DB, one could store entities (such as organizations in your case) and relationships between them in the form of nodes and edges. By having your data stored this way, you can easily interrogate your data for insights that might not be easily done using standard relational data systems.
Free ebook describing the need for graph storage and the common problems solved by such a datastore
Say, that you wish to store information about organizations, individuals working for those organizations, their job roles etc. You can do this by creating Nodes and relationships like the following:
(Person:"Joe Bloggs")-[:WORKS_AT]->(Organization: Google)
(Person:"Joe Bloggs")-[:WORKS_AS]->(JobRole: "Software Developer")
The above describes a person called Joe Bloggs that works for Google as a software developer. You can use Ciper query language (official language used for querying Neo4j) to get all software developers working for google.

Persistence Layer In SaaS Application

I have planned a SaaS Application for which we have selected Java for building the back end ,not yet selected which frameworks to utilize and I have opted to use either Ember JS with Bootstrap or Foundation with Bootstrap or Angular JS with Bootstrap for building the front end of the application.
I am confused with the persistence layer that either I should go for traditional Relational databases or should I go for 'Nosql Database' .
The idea is simple and straight ,offering Highly Configurable School Management System in SaaS model.The module at first I will be working on is Time and Attendance tracking of School/Universities/Colleges/Coaching Centers etc.As you can see that the policy of attendance (late,absent,present) varies from school to school ,university to university ,within university department to department ,within department teacher to teacher ,and coaching to coaching etc .And our application is not going to be deployed to their respective servers and will be hosted at cloud so one application running Accommodating dynamic policies running in isolation from the other.
My data is expected to grow with the period of time ,at fast pace since every school/coaching/institute will contain data of the following and following entities will be using the Application,Parent ,Student,Teachers,Principles,person who wants to take admission,Peons,etc
I have read answers to questions posted for the same kind of query and I found that people have used relational databases for this kind of application but they have built it 5-10 years back when there was no concept of Nosql databases ,All we knew was relational,object oriented databases so it would not be wrong to say that they opt the stack that was available at that time
I think that you should go for relational databases and I don't see any need of using Nosql databases ,the schema you will be having is static I am sure and you will be needed to maintain complex relationships as well.
Have a look at 'Multi tenant Architecture' ,and I would suggest you to use one database per client against one db per all clients.
Lets see what others would recommend you.

Should I use multiple databases in this situation (Ruby on Rails)

Through my companies website, our users can make artwork requests. Currently they are just being emailed to a single person.
I have been developing a separate application we'll call it "artwork manager", that will queue these artwork requests for our in house artists, and they will be passed out accordingly.
Our company website database contains the art_request table that this other application needs access to.
The "artwork manager" application only has an artists, art_doc, and awards, tables.
Should I just add these tables to our company website, and connect to that database? Or would it be best to use a separate database for each application? They are both being hosted on the same server.
Don't separate your databases, it will create a lot of confusion on development later. I strongly suggest merge it to one application.