This project has moved. For the latest updates, please go here.

What is the MemoryLifter Server

1. Introduction

The MemoryLifter Server allows you to manage many Learning Modules from a central location. You can create any number of user accounts and set up special groups (e.g. Administrator, Teacher, Student...).

2. How to use the MemoryLifter Server

There are several ways for MemoryLifter clients to connect to a MemoryLifter server. See the following graphics, for an overview of each method.


2.1   Direct database access:
image

This figure shows how direct database access works. The PostgreSQL database is installed and configured on a server. Now all the MemoryLifter clients (Student1 – Student4 and Teacher1 – Teacher2) can access the database with the MemoryLifter software. It is possible to assign different groups to the users. For example:

  • Group Student: Allowed to open and learn Learning Modules. Not allowed to add/edit or delete cards or Learning Modules.
  • Role Teacher: Allowed to open and learn Learning Modules. Allowed to add/edit and delete cards or Learning Modules.

The Administrator can be a MemoryLifter user, who has additionally permission to change global settings with the Admin Suite.

Notice: The user groups Student and Teacher are not PostgreSQL database user groups. They are fully handled by the MemoryLifter client.

Advantages of direct database access:

  • Easy install and configuration of the environment.
  • Very fast access to the database (noticeable when opening the MemoryLifter start page and when editing cards)
  • Easy adjustment of user groups. For example: the user Student1 wants to create a Learning Module. The administrator can give him the permission to do so by using the MemoryLifter Admin Suite.

Disadvantages of direct database access:

  • The students and teachers have read and write access to the database, which contains all Learning Modules. It would be possible for them to use a PostgreSQL administration tool to change the Learning Module data!
  • Direct database access should only be used for internal network (intranet) use, as we do not recommend giving access to the database server via the internet!

2.2 Database access via MemoryLifter Web Service:

image

This figure shows how database access via a MemoryLifter Web Service works. In contrast to direct database access, the users Student1 – Student4 are connected via a service to the database. Furthermore this mode allows the users Student5 and Student6 to connect via the internet to the MemoryLifter server.
If a user wants permission to add/edit or delete cards or Learning Modules, the user needs direct database access. The users Student1 – Student6 are not allowed to add/edit or delete learning content. This behavior can not be changed. If a student wants to have write access, the students needs direct database access.
As in direct database access mode, the Administrator can be a user of MemoryLifter, who additionally has permission to change settings with the Admin Suite. The big advantage of this mode is that users can learn from anywhere they are, without changing anything on the server.
 
Advantages of database access via the MemoryLifter Web Service:

  • The students can access to their Learning Modules from all over the world without security concerns.
  • Depending on synchronization settings, students can also learn without being connected to the MemoryLifter web service.
  • It is very easy to give new students an access to the Learning Modules.
  • For students it's not possible to change the Learning Module data on the database, because the MemoryLifter Web Service does not allow access to the database.

Disadvantages of database access via the MemoryLifter Web Service:

  • All users who want to add/edit or delete cards or Learning Modules need direct database access.
  • The connection is a little bit slower than with direct database access (noticeable when opening the MemoryLifter start page)

Of course it is possible to run the MemoryLifter web service on another server than the database itself. For this you just need to add another IP address to the connection list of the database.

Last edited Feb 27, 2012 at 12:23 PM by CFI, version 4

Comments

No comments yet.