Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Novice Question: get information from names.nsf
- Thread starter ns00h
- Start date
If you are a real beginner, you've come to the right place. There are a lot of competent people here that can help you, but you need to ensure that we understand the scope of the project correctly in order to give useful advice.
You wish to retrieve info from one Notes db and display it in another Notes db ? In that case, I can think of two wyas to get it done :
1) either you create a view with the data you want and export that data to a file, in order to import it into another db,
or
2) you create a Notes agent that copies the info you wish to display into documents in the new db, refreshing that info every once in a while.
Solution 1 is good for a one-time run. Solution 2 can be implemented with refreshing the data in mind.
That said, each of these solutions require Developer skills. If you have no Developer available, you will have to learn
.
So, which one of these solutions seem to better solve your problem ?
You wish to retrieve info from one Notes db and display it in another Notes db ? In that case, I can think of two wyas to get it done :
1) either you create a view with the data you want and export that data to a file, in order to import it into another db,
or
2) you create a Notes agent that copies the info you wish to display into documents in the new db, refreshing that info every once in a while.
Solution 1 is good for a one-time run. Solution 2 can be implemented with refreshing the data in mind.
That said, each of these solutions require Developer skills. If you have no Developer available, you will have to learn
.So, which one of these solutions seem to better solve your problem ?
- Thread starter
- #3
Thanks for the info.
Yes I am a real beginner. I think option 2 is what I want.
I wanted to create a kind of internal contacts database that would extract name, address, fax, phone, location etc. from names.nsf and display in another db. If changes were required they would be updated by the administrator in the names.nsf.
As I am a beginner can you recommend any good books that start from scratch and move on in a kind of tutorial style.
TIA
Nathan
Yes I am a real beginner. I think option 2 is what I want.
I wanted to create a kind of internal contacts database that would extract name, address, fax, phone, location etc. from names.nsf and display in another db. If changes were required they would be updated by the administrator in the names.nsf.
As I am a beginner can you recommend any good books that start from scratch and move on in a kind of tutorial style.
TIA
Nathan
Well, the names.nsf IS the internal contacts db.
What is this db to be used for ? Do you want to construct some special views to sort the info ?
Since you say that admins will do modifications in the names.nsf, what use is there to make another db just for viewing the info ?
What is this db to be used for ? Do you want to construct some special views to sort the info ?
Since you say that admins will do modifications in the names.nsf, what use is there to make another db just for viewing the info ?
- Thread starter
- #5
I suppose this is what I am asking.
In our intranet I want to have a company wide contacts list. I don't want all users going into names.nsf to view and edit data, so I guess I just want to pull the info from the names.nsf and display in web page. In particular the work tab in the person document. And they would probably want to be able to search this info for the contact they are after.
Is it a problem to build your own views? What happens when you want to upgrade?
TIA
Nathan
In our intranet I want to have a company wide contacts list. I don't want all users going into names.nsf to view and edit data, so I guess I just want to pull the info from the names.nsf and display in web page. In particular the work tab in the person document. And they would probably want to be able to search this info for the contact they are after.
Is it a problem to build your own views? What happens when you want to upgrade?
TIA
Nathan
Company-wide contact list on intranet.
If its in a web page, there really is no issue.
All you need is to create a frameset, and include the person view (or a specially-formatted view) in that frameset.
Enable the db to view the frameset when opening the db from a browser, and you are just about done.
From an intranet, users are supposedly anonymous.
The only person who can edit all docs is the admin, so there is no security issue in allowing intranet access to names.nsf.
To really lock things down, you could eventually copy the Person form to a WebPerson form, changing all fields to Computed When Composed, and insert a Form Formula into the specially-formatted view to call the WebPerson form when opening a document.
In that way, even with manager rights to the db, viewing the doc from the intranet will not allow changing document values in any way.
That said, you do raise an issue with upgrading.
Upgrading is very much the Ugly Duckling in Notes. The best you can do is mark all your special forms, views, and frameset to Not Allow Modification when Replicating or doing a Design Refresh, and then hope for the best for the next rollout of Notes.
I would create a special template containing only the elements you have modified. The next time the Notes server is updated, you can recopy those elements right after the upgrade, before even getting the server back online, and you are done.
Just don't forget to configure the db to show the frameset from the web !
If its in a web page, there really is no issue.
All you need is to create a frameset, and include the person view (or a specially-formatted view) in that frameset.
Enable the db to view the frameset when opening the db from a browser, and you are just about done.
From an intranet, users are supposedly anonymous.
The only person who can edit all docs is the admin, so there is no security issue in allowing intranet access to names.nsf.
To really lock things down, you could eventually copy the Person form to a WebPerson form, changing all fields to Computed When Composed, and insert a Form Formula into the specially-formatted view to call the WebPerson form when opening a document.
In that way, even with manager rights to the db, viewing the doc from the intranet will not allow changing document values in any way.
That said, you do raise an issue with upgrading.
Upgrading is very much the Ugly Duckling in Notes. The best you can do is mark all your special forms, views, and frameset to Not Allow Modification when Replicating or doing a Design Refresh, and then hope for the best for the next rollout of Notes.
I would create a special template containing only the elements you have modified. The next time the Notes server is updated, you can recopy those elements right after the upgrade, before even getting the server back online, and you are done.
Just don't forget to configure the db to show the frameset from the web !
- Status
Similar threads
