Map exportieren

Chapter 6: Working Together with Colleagues: Sharing Maps, Boxes and Material

Edumaps

Orientation

1

Why work together?

  • Edumaps is useful not only for teaching with students, but also for collaboration within the staff.
  • For example, you can:
    • collect materials together
    • prepare teaching units
    • coordinate tasks for parallel classes
    • document training content
    • prepare parents’ evenings
    • organize subject team work
  • The advantage:
    Everyone works in one central place and keeps the structure in view.
  • ⚙ start
2

Three forms of collaboration

  • There are several ways to work together with Edumaps.
  • 1. Edit one map together
    Good for subject teams, teams and projects.
  • 2. Copy content
    Good when everyone needs their own version.
  • 3. Embed content
    Good when central content should remain up to date in several places.
  • This pinboard explains the differences.
3

Example: subject team map

  • A subject team map could be structured like this:
    • Column 1: Grade 5
    • Column 2: Grade 6
    • Column 3: Materials
    • Column 4: Assessments
    • Column 5: Agreements
  • Each teacher can add their own materials or use existing boxes.

Edit together

4

Share a map with colleagues

  • If several teachers should work on the same map, share the map with edit rights.
  • Typical steps:
    1. Open the map.
    2. Open the sharing function.
    3. Select user or group.
    4. Grant edit rights.
    5. Briefly explain what the map is for.
  • Tip:
    Grant edit rights deliberately. Not every person needs write access.
5

Read or edit?

  • Before sharing, consider:
  • Read access is enough when colleagues should only view or use materials.
  • Edit access is useful when colleagues should:
    • add new boxes
    • update tasks
    • upload files
    • maintain shared lists
    • correct content
  • Tip:
    For larger teams, clear agreements are important: Who edits which column?
6

Set shared rules

  • A shared map works better with simple rules.
  • Examples:
    • Every box gets a clear heading.
    • Materials are sorted by grade level.
    • Outdated content is marked or deleted.
    • New tasks are added with a date.
    • Important notes are placed at the top.
  • Tip:
    Create an info box called “How we work with this map”.

Copy & embed

7

Copy box

  • When you copy a box, a separate new version is created.
  • This is useful when you want to:
    • adapt material
    • change a task for your class
    • reuse a template
    • work independently of the original
  • Important:
    Changes to the original do not affect the copy.
8

Embed box

  • When embedding, the content remains connected to the original box.
  • This is useful when central content should stay the same in several places.
  • Examples:
    • central school rules
    • shared assignment
    • current weekly plan
    • subject team information
    • link list
  • Important:
    When the original changes, the embedded display changes automatically as well.
9

Practical example: Control one central task in several student maps

  • Embedding is especially helpful when a task should appear in several places but remain centrally up to date.
  • Example:
  • A teacher creates one central task box for a project.
  • This box is embedded in several class maps.
  • If the deadline, link or instruction changes, the teacher edits only the original box.
  • All embedded versions are updated automatically.
  • This prevents different versions of the same task from circulating.
10

Copy or embed?

  • Use this rule:
  • Copy when each teacher needs their own editable version.
  • Embed when the same content should remain centrally controlled.
  • Examples:
    • Worksheet adapted for one class → copy
    • Official information for all classes → embed
    • Personal lesson variant → copy
    • Current weekly assignment in several maps → embed
  • Tip:
    Discuss in the team which content should be copied and which should remain central.
11

Copy map

  • A complete map can also be copied.
  • This is useful when:
    • a template should be reused
    • a teaching unit should be adapted
    • a colleague wants their own version
    • a map should be developed further independently
  • Important:
    A copied map is an independent version. Later changes in the original do not automatically appear in the copy.

Organization

12

Material collection in the staff

  • A shared material collection helps avoid duplicate work.
  • Possible columns:
    • Grade levels
    • Topics
    • Worksheets
    • Media
    • Links
    • Assessments
    • Good examples
  • Tip:
    Use clear titles and tags so colleagues can find material again later.
13

Team map for projects

  • For projects, a team map can bundle all important information.
  • Possible content:
    • timeline
    • tasks
    • responsibilities
    • files
    • meeting notes
    • links
    • results
  • Tip:
    Add a box at the top with current next steps.
14

Avoid versions

  • Many teams lose time because several versions of the same material circulate.
  • Edumaps can help by:
    • collecting material centrally
    • using embedded boxes for central content
    • making the latest version visible
    • reducing email attachments
    • documenting agreements
  • Tip:
    For official or repeatedly used content, use a central source instead of many copies.

Practice

15

Mini task: Plan a staff map

  • Plan a map for collaboration in your team.
  • Task:
    1. Choose a topic, for example a subject team or project.
    2. Decide which columns are needed.
    3. Create an info box with rules.
    4. Decide who gets read access.
    5. Decide who gets edit access.
    6. Choose one box that could be embedded elsewhere.
  • Goal:
    The map should support collaboration instead of creating more confusion.
16

Typical mistakes

  • Typical mistakes are:
    • Too many people get edit rights.
    • No one knows who maintains which content.
    • Copies are made although central content would be better.
    • Embedded boxes are edited without understanding the effect.
    • Old material is not marked.
    • The map has no clear structure.
  • Tip:
    Start with a small, well-structured team map.
17

Checklist for team maps

  • Before a team map is used, check:
    • Is the purpose clear?
    • Are the columns understandable?
    • Are rights set correctly?
    • Is there an info box with rules?
    • Are important materials easy to find?
    • Is central content embedded where useful?
    • Is someone responsible for maintenance?
  • A good team map saves time because everyone knows where current material is stored.