Forum Activity for @researchcooperative

How to set up designer form fields - is an overall summary of strategy possible?

Using Jamroom


Thanks... yes, this does explain what I was suggesting.


In my case, my Regular Users quota makes users "Power Users" who can make more than one profile. This power may be useful for members who can offer more than one kind of service, as editors and translators, for example, or as researchers and editors.

This leads to a further issue that I have been trying to get to grips with, namely how to provide different profile fields for different quotas?

If users can sign up for different quotas, and be (for example) "Power users" within different quotas, then a field that is intended for Quota A profiles created by Quota A power users may be seen by Quota B power users who signed up for Quota B and do not need the Quota A field in their profiles.

Perhaps the general rule here is to make the access to quotas and to profile fields as precise as possible.

We must be careful about unintended overlap in access to to a Profile field when we let the field be seen by the different user categories in the "Display Groups".

Unintended overlap in who sees which profile fields when creating and editing profiles becomes more likely if a single user can create profiles in more than one quota, and is thus a power user in more than one quota.
updated by @researchcooperative: 12/22/16 08:57:48PM

How to set up designer form fields - is an overall summary of strategy possible?

Using Jamroom

For me, the form designer is central to the social purpose of the network, because it is (a) where site members can tell other site members about themselves in a structured way, by setting up a personal and public profile, and (b) new visitors who are not yet members can see what kind of people have joined the network.

I am trying to balance what I consider to be essential (required) information for a public profile, with giving members freedom to say more or less about themselves using the optional fields.

Thanks
updated by @researchcooperative: 12/22/16 06:38:20PM

How to set up designer form fields - is an overall summary of strategy possible?

Using Jamroom

Specific issue:
What is the result if display option for a profile field is set to “All Users, including logged out” ? When I am logged out of my network, I cannot see a profile field that is 'displayed' in this way - so what is the meaning of the option when we are setting up a designer form field?

General issue:
After one year, I am still struggling with how to set up fields in the designer forms for accounts and profiles, and how the fields in each area relate to each other, to account holders, to administrators, logged-in network members, and non-logged in site visitors.

With all of this, I am trying to understand what the optimal combination of settings might be, that I can make as a site administrator.

Specific aspects of the problem have been addressed from many different angles in the various support forum threads, but I have not seen any overarching explanation or summary of how best to set up the designer forms, for one or more common scenarios of JR usage.

I presume this is because so many different variables are involved. I would also love to see basic example sites (model sites) that somehow illustrate what can be done by setting up the designer fields in different ways.

I have attempted to make a summary myself.

Please see the attached table that tries to put everything together on one page. Comments inside the table have labels to assist discussion of different parts of the table.

updated by @researchcooperative: 03/25/17 03:51:49AM

Invitations module does not have documentation

Using Jamroom

Hi - this thread seems to be concerned with two different issues:

1. JR invitations module used to invite followers (existing network members) to view site content that has been provided by the person making the invitation.

2. Inviting people who are not network members to join the network.

I do not see anything in the JR Invitations module that allows non-members to be directed to a sign-up page.

How to search member accounts?

Using Jamroom

Thanks very much - you have answered two questions in one.

Firstly, the Data Browser for the user module covers all the user account data, so we can search across all the fields directly - and we can do this while looking at the "Browser view" with just a single line of summary information showing for each user, or in "View Keys" mode which shows all the data fields with or without data in them. i.e. This is the admin-only search across user account data that I was looking for.

Secondly, we can edit (modify) user account data directly when viewing this information in the "View Keys" mode... which is really a back-end access route. Of course, this power should not be abused, but it does allow editorial/curatorial oversight when users make obvious spelling mistakes, for example.

I had previously tried to edit user account data when viewing individual profiles and their account holders, from the profile page, but that did not work. Password protection of account data also applies to Admin. when profile pages are viewed from the front end.

How to search member accounts?

Using Jamroom

Thanks,

I am referring not to the profile fields but the user account fields that only Admin has access to.

Since I have multiple user account fields, it would be useful for me, as Admin, to be able search for members based on information in their user accounts.

Thanks

How to search member accounts?

Using Jamroom

Currently we can search member account data only by the known name or known email address of an account holder, when looking at the member list in ACP. Yet the account details of members may contain much more information depending on what signup questions and account setting fields are provided.

How can we conduct a search across all members using account data fields in total, all at the same time?

This might require only a simple tweak of a skin .tpl file somewhere.
updated by @researchcooperative: 03/19/17 04:39:33AM

"Followers" and "Followers to Friends"

Using Jamroom

Both of these modules require users to approve a follower or friend, but perhaps the difference can be expressed with this imaginary skit:

Nobel Prize Committee to Bob Dylan:
"We would like to be your friend! Can we have your phone number? Then we can talk to each other. We have something important to discuss with you."

Bob Dylan to Nobel Prize Committee:
"No way! If you like my stuff, you can follow me and receive updates about my new songs - but I like my privacy. No one gets my phone number!"

Moral of the story: A follower can be accepted, but the gesture is not necessarily reciprocated. I might not want to follow you, even if I let you follow me. You can listen to me, but I don't have time to listen to you.

When I accept a new friend, or someone accepts me as a new friend, the connection becomes two-way immediately.

Question for JR team: Have I understood the system, or is this just hot air blowing in the wind?
updated by @researchcooperative: 02/22/17 02:07:06AM

During import from Ning to JR, what happens to attached documents (e.g. pdf files)?

Ning To Jamroom

Thanks. This will certainly be useful.

Part of my problem is that I have undoubtedly imported links that were already dead, so that changing the base URL will not bring them back to life.

In the lovely new JR site, I have many years of chaff to winnow out, not to mention entire bundles of rotting straw.

I will call this thread solved, for the moment. Thanks.
updated by @researchcooperative: 11/21/16 06:56:56AM

About the Update Base URL tool (inside the Ning Import module)

Ning To Jamroom

The only description I can find for the Update Base URL tool is:

"This function changes the base url for imported text strings that reference files in the Ning Archive. Use this tool if you have moved your imported Ning site to a new domain or a new folder."

This describes my situation, but I would be grateful for more specific information on how exactly the tool works with existing URLs that need to be updated.

My impression is that it works well when we need to replace a simple URL such as (A) with an equally simple URL that says (B):

(A) sitename.olddomain (B) sitename.newdomain

But if a URL has the following form (C), will it be changed to (D) if when we ask the tool to change (A) to (B)?

(C) sitename.olddomain/notes (D) sitename.newdomain/notes

And if a URL has the form

(E) sitename.olddomain/notes/specific-note-name

and needs to be changed to

(F) sitename.newdomain/profile-name/ningmemo/specific-note-name

can we do this by asking the tool to update from

(E) sitename.olddomain/notes/specific-note-name

to

(G) sitename.newdomain/profile-name/ningmemo/

??

Or to ask the question more simply, does the term "base URL" refer only to the URL part that ends with a domain name, or does it refer to any length of URL up to -- but not including -- the last part of the URL sequence defined by slash marks?

e.g. can

sitename.domain-name/X/Y

be regarded as a base URL for

sitename.domain-name/X/Y/Z ??

updated by @researchcooperative: 02/20/17 08:33:48AM